Method and system for providing synchronization of directory data

ABSTRACT

Methods and systems for providing synchronization of directory data between directory servers are provided. Example embodiments provide a Application Workspace System “AWS,” which enables users to access remote server-based applications using the same interface that they use to access local applications, without needing to know where the application is being accessed. In one embodiment of the AWS, every data entry in the LDAP is automatically replicated to the other directories using XLDAPS technology. In one embodiment, XLDAPS uses XSLT transformation rules to synchronize LDAP changes to different LDAP Directories which may have a different LDAP Schema and a different LDAP Directory Information Tree structure This abstract is provided to comply with rules requiring an abstract, and it is submitted with the intention that it will not be used to interpret or limit the scope or meaning of the claims.

TECHNICAL FIELD

The present invention relates to methods and systems for providing ansynchronization of directory data and, in particular, to methods andsystems for automatically providing seamless synchronization ofdirectory data between different directory server implementations.

BACKGROUND

Multiple waves of technology have left most organizations with ITinfrastructure that is complex, inflexible, and expensive to run.People, devices and applications are tightly coupled making it difficultto rollout new applications or support new work patterns. ITorganizations within corporations have to manage a hundreds if notthousands of applications, based on divergent technologies, and runthousands of PCs and servers, each with its own operating requirementsand idiosyncrasies.

Maintaining software on a distributed PC or other access device isexpensive and time-consuming. As the number of applications and servicesprovided through the PC, the complexity of the PC configurationincreases.

Historically this problem has been addressed by ‘locking down’ the PC tolimit the changes that can be made to it. Products have also beenintroduced to ‘push’ software to physical devices but these approachesdepend on there being a small, well-defined number of access devices aswell as a relatively infrequent update cycle. Until a few years ago thiswas difficult but achievable in a well managed environment. However, anexplosion in the number and type of access devices (which now encompassPCs, laptops, PDAs and mobile phones) combined with a need for frequent,real-time updates (to protect against viruses, worms and securityloopholes) has rendered such an approach unworkable.

In large organizations, the problem of access device diversity iscompounded by the fact that end users use applications that run on manydifferent platforms. Some run on the user's PC, some run centrally asterminal applications, thin clients or web services and some run onvirtual machine technology. Previously, the infrastructure forsupporting and managing these applications was entirely separate.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example screen display of a virtual workspace presented ona computing device that has an integrated Application Workspace Systemclient.

FIG. 2 is an example screen display of a virtual workspace presentedthrough a web browser interface to an Application Workspace System.

FIG. 3 is an overview block diagram of an Application Workspace System,including example components of example Application Workspace System webservices.

FIG. 4 is an overview block diagram of example components of exampleApplication Workspace System client services.

FIG. 5 is an example screen display of a component of an ApplicationWorkspace System client for monitoring and configuring aspects ofApplication Workspace System client systems.

FIG. 6 is an example overview flow diagram of processing performed by anexample Application Workspace System on a managed computing system.

FIG. 7 is an overview block diagram illustrating how the components ofan example embodiment of an Application Workspace System cooperate totransparently provide correct applications to users and to implement avirtual workspace.

FIGS. 8A-8F are example screen displays illustrating how a user operatesthe virtual workspace provided by an example Application WorkspaceSystem on a managed computing system to launch applications.

FIGS. 9A-9L are example screen displays illustrating how a user operatesthe virtual workspace provided by an example Application WorkspaceSystem through a web portal to launch applications.

FIG. 10A is an example flow diagram of the client side processing in anexample Application Workspace System performed when launching a remoteapplication from a managed computing device.

FIG. 10B is an example flow diagram of the server side processing in anexample Application Workspace System performed when launching a remoteapplication from a managed computing device.

FIG. 11 is an example screen display of a user interface on an unmanagedcomputing device for performing session management of sessionscontrolled by an example Application Workspace System.

FIGS. 12A-12D are example block diagrams of the interrelationshipsbetween Application Families, Applications, Application Folders, Users,User Groups, User Folders, Packages, and Package containers used toprovide the AWS application abstraction model.

FIG. 13 is a block diagram of the internal data model used by oneembodiment of a Node Manager component of an example ApplicationWorkspace System.

FIG. 14 is an example screen display of a user interface provided by anexample AWS Web Services for configuring application family objects inan example configuration repository.

FIG. 15 is an example screen display of a user interface provided by anexample AWS Web Services for associating application objects andapplication families with users in an example configuration repository.

FIG. 16 is an example flow diagram of an administration process providedby an example AWS Web Services for configuring an application object inan example configuration repository.

FIG. 17 is an example screen display that shows various properties thatcan be set for a package.

FIG. 18 is an example screen display that illustrates the assignment ofa script to a package based upon a pre-defined script events.

FIG. 19 is an example screen display of a script used to configureapplications.

FIG. 20 is an example screen display of a debugger of an exampleApplication Workspace System used to debug a script.

FIG. 21 is an example flow diagram of an event handling and scriptinvocation mechanism provided by the client side of an exampleApplication Workspace System.

FIG. 22 is an example screen display illustrating user level name valuetuples usable by AWS scripts.

FIG. 23 is an example screen display illustrating application level namevalue tuples usable by AWS scripts.

FIG. 24 is an example overview flow diagram of processing performed bythe client side of an example Application Workspace System when a logonevent is detected on a managed computing device.

FIG. 25 is an example flow diagram of processing performed by an exampleweb services component of an example Application Workspace System toretrieve entitlements information from a configuration repository.

FIG. 26 is an example flow diagram of processing performed by an exampleweb services component of an example Application Workspace System toresolve entitlements for remote applications.

FIGS. 27A-27B are an example flow diagram of processing performed by anexample client component of an example Application Workspace System toresolve entitlements for a managed computing device.

FIG. 28 is an example flow diagram of a routine to adjust an applicationobject vector.

FIGS. 29A-29B are an example flow diagram of processing performed by anexample client component of an example Application Workspace System toprocess application objects in preparation of installation and upgrade.

FIG. 30 is an example screen display of a virtual workspace presented toa user after the automated configuration processing performed by anexample client component of an example Application Workspace System.

FIG. 31 is an example flow diagram of processing performed by an exampleclient component of an example Application Workspace System to processuser selections to install or upgrade optional applications.

FIGS. 32A-32B are an example flow diagram of the overall processingperformed by an example client component of an example ApplicationWorkspace System to install or upgrade an application instance.

FIG. 33 is an example flow diagram of processing performed to installmissing (new or replacement) packages on a managed computing device.

FIG. 34 is an example screen display of a portion of user configurationdata stored by example client component of an example ApplicationWorkspace System on a managed computing device.

FIG. 35 is an example screen display of the installed package set in acomputing system repository of the same computing device shown in FIG.34.

FIG. 36 is an example screen display of remote monitoring of a managedcomputing system in an example Application Workspace System.

FIG. 37 is an example block diagram of a general purpose computer systemfor practicing embodiments of a Application Workspace System.

FIG. 38 is an example block diagram of detailed service side componentsof an Application Workspace System and their interactions to provide theservices described here.

FIG. 39 is an example block diagram of a general message bus as used byan Application Workspace System.

FIG. 40 is an example block diagram that illustrates how AWS GridLocation Services work within a LAN and across LANs.

DETAILED DESCRIPTION

Embodiments of the present description provide enhanced computer- andnetwork-based methods and systems for determining applications to whicha user is entitled and providing seamless and uniform access to theseapplications, regardless of their type and where they are accessed from.Example embodiments provide an Application Workspace System (“AWS”),which enables users to access remote server-based applications (e.g.,thin client applications, terminal server applications, applications onhosted operating systems, etc.) using the same interface that they useto access local applications, without needing to know where theapplication is being accessed. The AWS includes a set of client andserver components that implement the notion of a user's virtualworkspace, which is presented to the user either seamlessly integratedinto the native user interface (such as Windows Explorer) or via a webportal which presents a virtual desktop.

The AWS automatically determines which applications the user is entitledto use, and then figures out automatically, based upon a variety ofparameters, which applications are to be made available to the user(resolved to version, particular package etc.), and whether they are tobe installed locally, or accessed remotely. Entitled as used hereinrefers to more than just a concept of access permissions—it involvesevaluating a series of rules that specify how applications have beenadministered for what users and to run in what environments. Theparameters that influence this decision define, for example, the user,the access point (the device from which the workspace is accessed), thedelivery method (remote, local, etc.) the user's entitlements,application administration parameters, etc. Applications can beassociated with users in a “generic” fashion so that they can be“dynamically bound” to a user's access at various times. Thus, the AWScan separate out the administration of applications to users generically(for example, assigning a word processing application to a user) fromthe administration of actual application implementations that correspondto different versions, packages delivery methods, etc. In this manner,seamless integration of both local and remote applications is madepossible.

In the case of applications that are installed locally, the AWS providesfor the customization of the configuration and behavior of suchapplications via scripts that hook system events such as login,power-down, etc. or disconnect or reconnect on terminal servers. In thecase of remote applications that are made available, for example,through a terminal server, extensive application behavior modificationis supported using a rules-based engine.

The AWS also provides a generalized message bus that can be used forload balancing and resource discovery.

In addition, the AWS provides a generalized LDAP replication mechanismusing XSLT stylesheets that can replicate data between heterogeneousschemas. The use of XSLT for replication is extendible to otherdirectory server mechanisms or other information consuming processesthat entail heterogeneous data organizations.

The following description details an example embodiment of anApplication Workspace System, called “Workspace” or Propero Workspace.Other implementations of the various principles, methods, techniques,components, protocols, etc can be incorporated to provide otherembodiments of an AWS. Thus, the present description means to includeall such possible embodiments of an AWS.

The Application Workspace System implements an abstraction referred toas a “virtual workspace” that integrates seamlessly into whatever deviceenvironment a user uses to access applications. On a personal computerrunning Windows, for example, once configured, applications appear asicons, which can be “opened” to start an application running (i.e., tolaunch an application). The AWS automatically configures the user'senvironment so that the user need not know the particular applicationthat is being run—from a version/package perspective or from a locationperspective—an application may be run locally or remotely.

FIG. 1 is an example screen display of a configuration portion of avirtual workspace presented on a computing device that has an integratedApplication Workspace System client. The user interface displayed is onethat is presented by the AWS in response to the user logging into thenative environment of the computing device (e.g., Windows). In FIG. 1,one of the applications is shown as already having been configured forthe user (Microsoft Office 2003 Remote) and two other applications areavailable for installation and customization. When the user finishesconfiguring the workspace, the native user interface (for example, theWindows desktop) is displayed with the applications that have beenconfigured automatically part of the desktop. The user launchesapplications the same way, without needing to know whether they arelocal or remote.

FIG. 2 is an example screen display of a virtual workspace presentedthrough a web browser interface to an Application Workspace System. InFIG. 2, a variety of remote applications are offered to the user asicons which can be selected to invoke the corresponding applications.When run, icons representing these applications appear in a task bar,just as if they were part of the native interface of the underlyingcomputing device.

The AWS abstracts the notion of an application so that the task ofassociating applications with users is separated from the administrativetask of mapping particular implementations of the applications todifferent access devices (from where the application is accessed and howthe application is accessed—e.g., a portable or desktop). For example,the directory services (e.g., LDAP) setup of application implementationmappings is an administrative task that need not involve lay users.

To accomplish this abstraction, applications are modeled as belonging toan “application family” that represents the application in an abstractsense (e.g., “Office”). Thus, for example, all kinds of differentversions of Microsoft Office may be abstracted as a single family“Office.” Specific applications that can be thought of as instances ofthose application families (called application objects) delivered viaspecific means (e.g., “Microsoft Office 2003—Local”, “OpenOffice forMac—Local”, “Microsoft Office 200—Remote”). This information is storedin an AWS configuration repository, which is typically an LDAPdirectory, although equivalent storage repositories, protocols, anddirectory servers may be used.

Stored within the application family object in the configurationrepository are a set of rules (sometimes referred to as “policy”) thatdescribes how an application family is to be resolved to a specificapplication instance at the point of use. Point of use (also referred toas point of access herein) refers to a description of the environmentwhere from the user is attempting to access a particular application.For example, a mobile device being used while traveling abroad typicallywill be characterized as a different point of use than the user's homepersonal computer. As a result, the AWS may desire to give the useraccess to a different application instance than the user normally useswhile at home.

Entitlements comprise the definitions (including all the attributes of)the set of application family objects, application objects (includingall relevant sub-objects such as document types and launch items),associated package container objects and package objects, along withtuples from all the users user groups, that a given user may haveavailable to him or her at any time. A set of entitlements for a usercan be derived from the AWS configuration repository. A process referredto as entitlements resolution further refines a set of entitlements tothe set of application objects (and hence the relevant associatedobjects from the set listed above) that a user actually has available tohim or her at a particular point in time.

Assignment of applications (in the general sense) to users isaccomplished by creating links in the AWS data model between users andapplication families—thus allowing for non-IT literate administrators tomanage which applications their users need to be able to use withouthaving to be cognizant of the various versions and delivery mechanismsthat may by appropriate at specific locations or from specific accessdevices (such as via a PC or a PDA).

The abstraction of applications breaks the administration ofapplications into two areas: user administration, which describes whichusers are associated with which applications families; and applicationadministration which is typically an IT (information technology)function that provides the rules indicating under which circumstances anapplication family resolves to a specific application. Note that useradministration may administer to any defined group instead of to anindividual user using any type of grouping mechanism. Groups may alsosubstitute for other entities in the AWS data model.

Note that, for the purposes of this description, the term “application”is used to mean a set of modules, code, script, text or otherrepresented code and/or programs that execute on either hardwaremachines or higher level virtual machines or are executed by otherprograms that overall allows a user to achieve some task using thecomputer (i.e., “apply the computer” to a task). Also, a “package” is aspecific set of modules, code, script, text or other represented codeand/or programs that execute on either hardware machines or higher levelvirtual machines or are executed by other programs that are deliveredtogether in some manner. Thus, an application comprises one or morepackages. Within an AWS configuration repository, “application objects”are used to represent applications, and “package objects” are used torepresent packages.

Note as well that the term “local” or “remote” with reference toapplications indicates where, relative to the user, processing occurs inorder for the user to achieve the task using the application. Note thatthis is distinct from where the user interacts with the applicationthrough an input device (e.g., screen, keyboard, mouse etc.) as the useof the input device typically will be on the computer the user isphysically interacting with.

When a user attempts to login to the user's environment, and at othertimes, the AWS attempts to automatically determine the virtual workspacefor that user from the point of access. In the case of a computingdevice such as a desktop computer, this determination process results inpresenting the user with a set of icons on the desktop that map toparticular applications. As an effect of this process, localapplications are properly configured, installed, removed, customized andpossibly updated, and remote application access is integrated into thevirtual workspace. That way, when a user “clicks” on an icon to invokethe underlying application, the “right” thing just happens, be it localor remote. Which applications are installed or configured is determinedbased upon a process referred to as “entitlements resolution.”

Entitlements resolution is the decision process that resolves anapplication family object to an application object so that thecorresponding application instance can be made available to a user. Thisis performed at the point of use, and has various pieces of informationmade available to it from the environment and from the AWS data model.Such information includes, for example, location, network address,access device type, pre-defined tuples (for example, name-value pairs)that may be stored on the access device, and tuples that are associatedwith any application object in the AWS data model.

Entitlements resolution typically takes place at a point of entry to thesystem—in many implementations, this can be one of two places:

-   -   An “intelligent” access device (e.g., a computing system that        can perform local processing and has elements of the AWS        installed on it); and    -   A remote interface—usually manifesting itself as a web        application, and commonly part of a web portal.        The entitlements resolution process can result in the AWS        needing to transparently install or configure or remove or        otherwise manage locally installed applications. It can also        result in automatically presenting to the user applications that        the user is able to use remotely (for example, if no local        application availability is present or, for example, to possible        override a locally installed application in favor of a remote        one). In order to achieve access to remote applications, any        icon or link representing the application includes an encoding        of a primary key of the application object in the configuration        repository (usually a Distinguished Name (a “DN”) to an LDAP        object). This identifying key is used to get information from an        AWS configuration repository regarding the details needed to run        the application.

Note that many different kinds of remotely accessed applications can beintegrated into an AWS. For example, an AWS can integrate and supportterminal server applications (which run applications in sessionsspecific to a client access and which are isolated from otherapplications), Citrix applications (which provide an extension to thegeneral case of Terminal Server applications), Terminal Emulators forcharacter based protocols, virtual machine environments such as hostedoperating environments using, for example, VMWare, on-demand applicationstreaming, and any other form of application delivery. The generaldistinction that the AWS draws between a “local” and a “remote”application is that a local application is some form of code, script orotherwise that executes locally on the user's computer in a mannernative to the local computer's native operating system to perform thefunctions of the application, whereas a remote application has some formof code, script, module or otherwise executing on a computer other thanthat which the user is using, and any code in that instance thatexecutes locally on the computer the user is using does so only toprovide screen, keyboard and mouse functionality for that remoteapplication.

If the entitlements resolution process results in providing a user withaccess to remote applications, then the mechanism by which they areactually launched (described in detail below) uses web-based componentsand systems that are common to both access from a workstation runningcomponents of the AWS (e.g., a managed workstation) and from aworkstation running a browser with a Java Virtual Machine that is usedto navigate to a web-based portal (e.g., an unmanaged workstation). Insome embodiments, the behavior of remote applications is automaticallymodified to behave properly when they are launched at their point ofuse. Behavior modification of applications is also described furtherbelow.

Different implementations of an AWS may present different sets ofcomponents and services to effectuate the notion of a virtual workspace.In an example AWS, the Propero Workspace (the “Workspace” or“workSpace”), includes a set of tools, modules, data schemas (datamodels) etc., which are delivered to customers as a set ofintegrate-able components and/or services. A typical AWS includes: amanager component; a server component; and an analyzer component.

The manager component comprises a set of modules downloaded to a clientmachine to allow a user to install and run applications locally (or as a“terminal” to remote applications), which are automatically configuredand customized on a per-user basis and for the user's environment. Anode manager component of the manager component provides a majority ofthe AWS support for installation and configuration, event based scriptcustomization of applications, and communications with the servercomponent.

The server component comprises the entirety of network (e.g., web)-basedcomponents that support access from intelligent workstations and accessfrom browsers (via a portal). These components include the ability toperform entitlements resolution, user administration, applicationadministration, application personalization and behavior modification,etc. and implement the virtual workspace.

The analyzer component comprise an extensive set of tools which are usedto assist administrators in determining mappings for applications toapplication families, exclusions, conflicts, dependencies, which usersuse which applications, etc. A kernel manager component of the analyzerperforms application usage based upon detecting a variety ofactivities—at levels of actual use—not just invocation—on bothintelligent workstations and on terminal servers. The detection occursby “hooking” various system code to be made aware when certain eventsare triggered.

Example embodiments described herein provide applications, tools, datastructures and other support to implement a Application Workspace Systemto be used for automatic and transparent configuration and customizationof applications and seamless integration of remote and localapplications in a virtual workspace. Other embodiments of the describedtechniques may be used for other purposes. In the following description,numerous specific details are set forth, such as data formats and codesequences, etc., in order to provide a thorough understanding of thedescribed techniques. The embodiments described also can be practicedwithout some of the specific details described herein, or with otherspecific details, such as changes with respect to the ordering of thecode flow, different code flows, etc. Thus, the scope of the techniquesand/or functions described are not limited by the particular order,selection, or decomposition of steps described with reference to anyparticular routine.

FIG. 3 is an overview block diagram of an Application Workspace System,including example components of example Application Workspace System webservices. In one embodiment, the AWS comprises one or more functionalcomponents/modules that work together to provide personalized andon-demand configuration of and access to local and remote application.These components may be implemented in software or hardware or acombination of both. In FIG. 3, a an Application Workspace Systemcomprises a client side, herein shown as managed workstation 301 andunmanaged workstation 302, and a server side, show as AWS Web Services310. A managed (or “intelligent”) computing device, such as managedworkstation 301 is a device (e.g., a Windows workstations) that hasinstalled on it an instance of the AWS Manager (described below withrespect to FIG. 4). An unmanaged computing device, such as workstation302 is a device with no AWS software installed on it, but does have abrowser and a Java virtual machine available to navigate to a portalprovided by the AWS Web Services 310. The Web Services component 310provides a variety of AWS components and services such as support forentitlements 311; information services 313 for access to theconfiguration repository 320, for example; session and connectioncontrol 312, for example to remote applications 340 needing terminalemulation or session management or to access hosted operatingenvironments 350; and security, authentication, and other supportservices 314. In one embodiment the configuration repository 320 forapplication configuration and association data is implemented by aLightweight Directory Access Protocol (LDAP) server.

FIG. 4 is an overview block diagram of example components of exampleApplication Workspace System client services. In one example embodiment,the client portion of the AWS that resides on a managed computing systemis known as the AWS Manager. The AWS Manager 401 comprises Node Manager410 that executes in the SYSTEM security context, and User SessionManager 420 that executes in the security context of the user, and anynumber of remote application support processes 422 that manage access toremote applications on the managed workstation. AWS Manager 401 alsocomprises local script, package, and configuration data repository 430whose data corresponds to the “state” of installed applications on themanaged workstation.

Note that the use of the term “workstation” is a matter of ease ofdescription is not meant to convey a specific arrangement of hardware orsoftware. Essentially, any computing device capable of performing thefunctions indicated can be substituted where this description uses theterm “workstation.” Thus, workstations may be mobile or wired device,embedded systems, PDAs, cellular devices, etc.

Node Manager 410 comprises a set of services, modules, and code forsupporting the functions of an AWS to implement a virtual workspace. Thenode manager provides all the necessary functions for packaging,installation, scripting, management, diagnostics, tracing and anyancillary functions that AWS uses. In particular, the Node Manger 410comprises event runtime and script object support 411; installation,scripting, monitoring, image comparison, and custom services 412;security support 413, and support for network communications 414, forexample with the AWS web services.

Note that in some embodiments, some of the code of the Node Manager 410,because it performs “smart” configuration, can also be used by terminalservers to configure remote applications made available through terminalservers, because many of the same functions are needed to configureremote applications. For example, the Node Manager code may also be usedfor Windows Terminal Servers and Citrix Servers as a system service.This shared code is mainly a figment of efficient implementation,though, and is not a requirement of an AWS.

The user session(s) instances 420 comprise all of the local supportneeded to interface to local and remote applications using AWS. Ittypically includes instances of the Node Manager session support 421that are specific to the user and the particular session; terminalemulation support 422 for interfacing to remote applications; a JAVAvirtual machine 423 (although other languages and virtual machines couldbe similarly incorporated); a web browser 424; and the configured userapplications 425. Other components can of course be present as well.

FIG. 5 is an example screen display of a component of an ApplicationWorkspace System client for monitoring and configuring aspects ofApplication Workspace System client systems. In some embodiments, thiscomponent is known as the Workbench or the AWS Manager Workbench.Workbench 501 provides a user interface to the packaging, diagnostic andother functions of the AWS Manager. The Workbench 501 can be run on aremote system and can be used to analyze, debug, and otherwise monitor amanaged workstation remotely. In FIG. 5, Workbench 501 is showndisplaying a package 502 that exists on a monitored managed workstation.The package contains several “features” 510 (as defined by the MSIpackage interface) and a set of events 511 to which scripts have beenassociated for this package. Event based scripts and their use toconfigure applications are described further below. The Workbench 501offers additional functions as shown in action hint list 520.

As mentioned, the components of the AWS are used to implement a virtualworkspace, which transparently “delivers” access to the rightapplication for the right user for the right point of access at theright time by abstracting out the notion of an application. To supportthis abstraction, the application information, mappings to otherobjects, application packages (which define how an application isconfigured/installed) etc. are set up in the configuration repositorytypically by an administrator. Application packages are discussedfurther below with respect to installation of local applications.Application packages can contain scripts that are automaticallytriggered upon the detection of certain system events (such as logon).Users can also be assigned to application families through theentitlements set up procedures. Once entitlements are set up, users usethe workspace to launch applications—in a manner with which they arefamiliar—and the “right” thing automatically happens. The node manageron a managed workstation or a browser invokes workspace (server)components to automatically configure the virtual workspace, processlaunch requests, configure applications, etc. In addition, a kernelmanager component runs in certain scenarios, such as on terminalservers, to ensure that applications behave properly when they are runremotely. In overview, the kernel manager configures remote applications(such as terminal server applications) to trap certain events, such asfile access requests, to ensure that applications behave properly asthey may have been written to operate as single user applications andnot share resources appropriately.

FIG. 6 is an example overview flow diagram of processing performed by anexample Application Workspace System on a managed computing system. Thesteps are typically performed by an AWS Manager component, such as NodeManager 410 of AWS Manager 401 in FIG. 4. Generally, the AWS client sidecode provides a variety of services on a managed workstation toautomatically configure and personal the set of applications intendedfor a user at the user's point of access when at the time of access. Thecode automatically configures the virtual workspace when it detects thatthe user has logged on, automatically installs/upgrades applicationsthat are selected by the user for installation into the virtualworkspace, takes care of launching applications, and responds torequests from a user to manage the user's remote sessions.

More specifically, steps 601-610 present an event handling loop. in step601, when the code detects a logon event, the node manager resolves theentitlements relevant to that user and access point (step 602),transparently installs or upgrades as necessary mandatory applications(step 603), including rebooting the system if the applicationinstall/upgrade requires such, and then presents a portion of thevirtual workspace with information to allow the user to furtherconfigure applications (step 604). FIG. 1 is an example screen displaythat results from the processing shown in steps 601-604. In step 605,when the code detects a request from the user to install/upgrade one ormore applications, then in step 606, the Node Manager resolvesentitlements and proceeds to install or update the indicatedapplications. In step 607, when the code detects a request from the userto “launch” (run or execute) an application, the Node Manager proceedsin step 608 to launch a local or remote application as indicated. Instep 609, when the code detects a request to manage a (for example,terminal) session, the Node Manager presents a user interface in step610 that allows the user to manage the session.

FIG. 7 is an overview block diagram illustrating how the components ofan example embodiment of an Application Workspace System cooperate totransparently provide correct applications to users and to implement avirtual workspace. In FIG. 7, a user uses a device 701 to access the AWSWeb Interface 702 (the applications portal) typically through DHTML(Dynamic HTML). In response, the AWS Web Services components 703 performentitlements resolution (to decide what application to run), consultingthe AWS LDAP directory service 704 as needed. The AWS LDAP server 704interfaces to and synchronizes configuration data stored in entitlementsdata repository 705. A user can use a managed device such as workstation706 to run either local applications or remote applications. Software(for example, a Node Manager) running on the managed workstation 706performs entitlements resolution via AWS Web Services components 703and, when indicated by the resolution process, installs localapplication packages configured from the local package and configurationrepository 707. Both the package and configuration repository 707 andthe AWS Web Services component 703 access and manage application packagedata stored in a master package repository 708. The AWS ManagerWorkbench 709 is used by and administrator to manage packages, monitorthe configuration process, administer entitlements, etc. Wherebeneficial, one or more test workstations 710 may also be incorporatedto test configurations of packages, etc.

Details of how an administrative sets up application packages forinstallation are described further below with respect to FIGS. 14, 15,and 16. Details of the entitlements resolution process are describedfurther below with respect to FIGS. 24-30.

FIGS. 8A-8F are example screen displays illustrating how a user operatesthe virtual workspace provided by an example Application WorkspaceSystem on a managed computing system to launch applications. FIG. 8Ashows a standard operating system desktop (native user interface) on amanaged workstation. FIG. 8B shows the user logging into the user'sdesktop using normal procedures. FIG. 8C shows how the AWS softwareintegrates seamlessly into the standard user interface of the nativeoperating system and shows the user that the user's applications areautomatically being “configured.” This is one typical point in time,where the entitlements resolution process is invoked to automaticallyconfigure local and remote applications for the user. After theentitlements resolution process is complete, a list of availableapplications which are available for local installation (based upon theusers entitlements set up by an administrator earlier) is displayed asshown in FIG. 8D. The resolution process may result in many (desired)side-effects as detailed below, since the AWS automatically candetermine compatibilities between applications, upgrades to newerversions etc. FIG. 8E shows example feedback during an applicationupgrade. FIG. 8F shows additional applications that can be installedshould the user desired.

Note that once the applications are installed/updated, the user canlaunch local applications on the managed computing device using thenative operating system mechanism. The AWS does not intervene. However,it is possible for someone (e.g., an administrator) to associateshortcuts with specific AWS events, and thus be able to perform customscript actions before applications are launched and at other times inthe system.

FIGS. 9A-9L are example screen displays illustrating how a user operatesthe virtual workspace provided by an example Application WorkspaceSystem through a web portal. For example, a user from a unmanagedworkstation, a PDA, a cellular phone etc. may login to the web portaland access applications remotely. (The backend mechanisms used tosupport web portal access typically are also used when a user launches aremote application from a managed workstation.) FIG. 9A shows the userlogging into the web portal through a uniform resource locatordesignation (URL). FIG. 9B shows the portal as it initially comes up,after several applications have been configured for that user. Basedupon a current set of entitlements for that user, the user has access toInternet Explorer, Lotus Notes, MS Word, My XP desktop, WindowsExplorer, and workspace Analyzer. These applications demonstrate a mixof the type of remote applications that can be served by a virtualworkspace—in this case, the majority are Terminal Server applications,whereas “My XP desktop” is a VM-Ware virtualized, hosted OS image. FIG.9C shows the AWS responding to the user indicating that the user wishesto launch MS Word (by, for example double-clicking) the MSWord icon. Atthis point, the entitlements resolution process to determine the correctapplication to run begins and the application is run. FIG. 9Dillustrates that a java virtual machine is being used to support the AWSin this current embodiment. In FIGS. 9E and 9F, the user is beingconnected to a server that can serve the application as a result of theentitlements resolution process. Appropriate user logons take place (forexample, via single sign-on techniques), as shown in FIG. 9G, to allowthe user access to the designated application. Notice in FIG. 9H, thevirtual desktop that appears in the user's browser. FIG. 9I shows MSWordlaunched on a remote computer and servicing the user through the virtualdesktop. The user interacts with MSWord just as the user would if theapplication were installed remotely. In FIG. 9J, the MSWord icon nowshows in the user's taskbar of the user's virtual desktop. FIG. 9K showsthat the user has invoked another application remotely, Lotus notes, ina similar manner. FIG. 9L illustrates what the virtual workspace lookslike when the user subsequently logs off the session.

As mentioned, a user can launch a remote application from a managedcomputing device as well. Each application object when configured by theAWS contains launch item objects and document type objects. For launchitem objects, these consist of a name (e.g., “Microsoft Word”), an icon,and a location attribute (e.g., “Program Files\Microsoft Office”). TheAWS Manager generates a shortcut in the location as specified in thelocation attribute, with the specified icon and name, but referencing aidentifier which is generated to include the address of a component inthe AWS Web Services, and encoded with a parameter which is set to theidentifying key of this launch item. As a result, when a user clicks onone of these shortcuts, a web browser is launched which sends a requestto the AWS Web Services which launches the remote application.

Typically, the access device is only aware of the identification key ofthe remote application. Note that it is common for these keys to pointto sub-entities of the remote application (c.f., with an installedapplication having more than one “icon” that starts a subcomponent ofthe application). These identification keys are coded into shortcuts orlinks on the desktop or, if applicable, the portion of the accessdevice's UI commonly used for application related links.

In addition, the system is configured with document types (also known as“file extensions” or “file associations” which are similarly linked toan identification key of the remote application that can handle thatdocument type. There may be various implementations of a shortcut, link,launch item or dock item that represents an identification key that allachieve a common purpose—namely that of notifying a component on theaccess device that the user has selected or “click” on that shortcut orlink.

When a user clicks on one of these links in order to request, or“launch” the associated application (or by selecting a document of atype configured to be associated with a remote application), theidentification key, encoded as a URL, is sent to the system AWS WebServices.

FIG. 10A is an example flow diagram of the client side processing in anexample Application Workspace System performed when launching a remoteapplication from a managed computing device. The processing in FIG. 10Ais performed in response to a user activating an icon (or document type)that refers to a remote application. Such icons or document types havereferences to the Distinguished Name (“DN”) of the remote applicationencoded within them as an identifying “key” and this reference is passedto the AWS Manager when the code of FIG. 10A is invoked. Thus, in step1001, the AWS Manager receive an indication of a DN and uses it in step1002 to request a url within the AWS Web Services portal. (The portal,in response, may launch a browser with that url.) At this point the AWSWeb Services takes over to figure out how to launch the specifiedapplication (see FIG. 10B). Sometime later, in step 1003 the AWS Managerreceives an indication of a formatted web page which it can then use tolaunch the application in an appropriate environment, for example, aterminal session. In step 1004, the AWS Manager executes the web pageand starts the “thin” application by rendering the information on thepage. This information (commonly in Dynamic Hyper-Text MarkupLanguage—DHTML) contains within it various script and objectinstructions to start a thin client application and to provide it withthe connection information as determined by the a connection managerwithin the AWS Web Services. In the example of an WTS (Windows TerminalServer), the thin client application is a component that connects via atunnel (VPN) to the WTS.

FIG. 10B is an example flow diagram of the server side processing in anexample Application Workspace System performed when launching a remoteapplication from a managed computing device. Typically, this processingis performed by one or more components of the AWS Web Services, forexample, components 311-314 in FIG. 3. In step 1005, the web servicereceives (from the AWS Manager) an indication of a user ID and anindication of the application (from the domain name/url). in step 1006,the web service determines that the user is entitled to the remoteapplication. If so, processing continues in step 1007, else returns anerror. In step 1007, the web service obtains information from aninformation services component (for example a directory service)regarding the application user, infrastructure location, etc. In step1008, the web service determines an appropriate backend (for example, asession manager) to handle the application request (e.g., one that cantalk to Terminal Servers, VMWare, etc.), and passes information onto thebackend. In step 1009, the web service determines whether to use anexisting session or not, and if so, continues in step 1011, otherwisecontinues in step 1010. More specifically, the code queries application(terminal) servers to see which one to use based on, for example, thenumber and type existing sessions, and load. In step 1010, having chosena server, the code prepares it for the forthcoming connection (if new)including passing the entitlements, printer mappings and application tolaunch. The target server is notified that a new connection to it ispending, and it awaits the client connection. Any information requiredfor the new connection (e.g., screen size) can be obtained from theconfiguration repository. Similarly, security and any additionalfunctions related to preparing for a connection from the client computerto the target server are performed. In step 1011, if it is to use anexisting session, then the application is started. In step 1012, the webservice can now respond to the request from the AWS Manager with anappropriately formatted page to allow the remote application (thinclient) to be launched.

Note that, similar to a managed computing device, when a user activatesan icon in a web page rendered by the AWS web server on an unmanagedcomputing device, the mechanism for launching the application issimilar. Most of the steps of FIG. 10B are executed, the designation ofthe user and application, however, arrive from the AWS web browserinterface.

In an AWS such as the workspace, users can view and manage existingsessions with remote applications. In the case of an unmanaged computingdevice, a user can use various user interface (“UI”) controls/elementsprovided by the AWS Web Services to view and manage existing sessions(such as disconnect them, reconnect them and to kill executing processeswithin them if available). In the case of a managed computing device,the AWS Manager interacts with the AWS Web Services to retrieve thesession data, and then presents this data using its own UI elements(usually handled by the Node Manager Session Support 421 in FIG. 4).

To perform session management on the unmanaged device, typically asession controller component of the AWS Web Services queries appropriateother components for any current sessions that exist for the callinguser. The session controller compiles a session list, and encodes eachsession into a Session ID that is unique across all sessions. Thissession ID has the form:

SessionManagerID;domain\\username(uid)/ID@serverDN:protocol.

The session controller parsers the SessionManagerID to locate acomponent responsible for the session then the rest of the text ispassed to that component. The domain and username identify the user, theID identifies the actual session itself on the backend server, theserver DN identifies the backend server in LDAP, and the protocol is thephysical protocol used to connect to that backend server (as somecomponents may support more than one protocol).

FIG. 11 is an example screen display of a user interface on an unmanagedcomputing device for performing session management of sessionscontrolled by an example Application Workspace System. In FIG. 11, onesession 1103 of type XP/RDP (a workspace Terminal Server session),containing one application (Lotus Notes) is currently displayed. Theuser can close (disconnect), reconnect, or perform advanced options byselecting links 1104, 1105, and 1106, respectively. Other than thereconnect operation, all of these operations typically only returnstatus information. When a user attempts to reconnect a session, loadbalancing is not performed. Instead, the session manager is instructedto which particular session to connect.

As mentioned previously, the AWS abstracts users from applications usinga concept of an Application Family. FIGS. 12A-12D are example blockdiagrams of the interrelationships between Application Families,Applications, Application Folders, Users, User Groups, User Folders,Packages, and Package containers used to provide the AWS applicationabstraction model. FIG. 12A describes the mapping between users, usergroups, and user folders. Users are individuals are stored as entitiesin a directory, containing standard fields like a user's name and logininformation. User entities also contain links to the applications thatthe user is entitled to use.

In order to make the administration of large numbers of users moreconvenient, they can be grouped together and managed as a single unit.There are two ways of performing this grouping: user folders and usergroups. User folders are structures akin to directory folders within afiling system. Each user is contained in a single user folder that mayin turn be nested inside a parent user folder. User folders provideinheritance. In the example shown in FIG. 12A, if the application“Excel” were assigned to the user folder “United Kingdom” and theapplication “PowerPoint” were assigned to the folder “London”, the user“Joe Bloggs” would be entitled to use both “Excel” and “PowerPoint”while the user “Jane Doe” would only be entitled to use “Excel”.

User groups are looser structures that allow users from anywhere in theuser folder structure to be grouped together, independent of that folderstructure. Like user folders, user groups can be used to assignapplications to multiple users at one time. User groups cannot be nestedinside one another, nor is there any inheritance between them.

Applications in the AWS separate the business-oriented concept of aparticular application (like “Microsoft Word”) from the technicaldetails of the package(s) that are used to deliver it (like“office2003.msi” and “office2003sr2.msi”). This separation allowschanges to be made to the way that an application is delivered withouthaving to change the entitlements of users to that application. As shownin FIG. 12B, there are three different application entities to allowflexibility in the specificity of application entitlements. These are:application families, application groups, and applications. For example,a user can just be assigned “Microsoft Word” to get the latest version,or be assigned a specific version such as “Microsoft Word 2003”.

Application families allow entitlement assignments without concern forwhich version or platform of the application is used. For example, theapplication family “Microsoft Word” could be linked to separateapplication instances for the Windows and Macintosh editions.Entitlements processing will ensure that users assigned “Microsoft Word”would get the appropriate edition for their platform.

Application groups allow a group of applications to be bundled togetherand assigned as a single unit. With the example shown in FIG. 12B, userscan be assigned the group “Front-office Applications” to get the latestversions of “PowerPoint” and “Excel” while stipulating a specificversion of “Access.”

Application instances describe specific versions of applications; theyare what is ultimately presented to users on the ‘Start Menu’ orelsewhere. Generally, application instances are only directly assignedto a user if the user requires a specific version of an application.

FIG. 12C illustrates a concept of packages and package containers.Package containers group together a mutually exclusive set of packages.This construction is needed to correctly manage the installation of MSIpackages. Note that other types of installation and packaging protocolsmay be used as package instances. Package instances correspond to asingle installable item, such as: special AWS Windows MSIs, StandardWindows MSIs, vendor-specific Windows SETUP.EXEs, and Macintosh PKGs.MSI is used as an exemplary package type for the description embodiedherein.

FIG. 12D is an block diagram showing how the abstractions described withreference to FIGS. 12A-12C can be mapped as entitlements. The AWS offersadvantages over prior systems in that it decouples the business viewfrom the IT view of delivering applications, and does so in a usercentric manner. For some examples:

-   -   “Office”, “Microsoft Office”, “Winzip”, “Business application”        and “Stuff” are all Application Families. Note that they do not        specify:        -   Platform        -   Version        -   Whether local or remote etc.    -   “Office 2003”, “Winzip 9.0” are all Applications. They are        specific major versions, and are for platforms.    -   Applications also contain information that specifies whether        they are local or remote. As a result, an Application also        embodies the delivery mechanism used for the application.    -   MSIs are Packages, as are vendor supplied MSIs.    -   A Package Container is a higher level object for Packages that        creates the notion of a group from within which 1 Package can be        installed at any time. The Package configuration object contain        information describing how to upgrade and remove them in the        case that another packages is to be installed.

So, while Application Families and Package Containers are the objectsthat are assigned (both in terms of an Application Class to a user, anda Package Class to an application instance), the AWS then decides basedon the runtime environment which application (and package if a localapplication) is actually required and installed. This installationinformation is then stored on the workstation and associated with theusers profile to allow for future decisions (such as exclusions) to bemade. Applications as modeled in the data model described by FIGS.12A-12D can contain dependencies and exclusions—dependencies areapplications that must be available locally if this application is to beavailable locally, and exclusions are applications that if already areavailable locally will prevent this application being made availablelocally.

The term “Application” or “Package” may be used to refer to theconfiguration item in the configuration repository representing theapplication or package or it may refer to the application or packageitself, depending upon context. In most cases, this description appends“object” when meaning the configuration item in the configurationrepository.

FIG. 13 is a block diagram of the internal data model used by oneembodiment of a Node Manager component of an example ApplicationWorkspace System. In this embodiment, the configuration repository isimplemented using an LDAP server (see FIG. 7, for example).

User objects are stored in hierarchy within the configurationrepository. In an embodiment that uses an LDAP implementation, the AWSuses standard LDAP schema concepts of Organizational Units (OUs) tosupport this abstraction.

User Group objects contain sets of DNs (Distinguished Names—the LDAPconcept of the primary key of an object) pointing to the users in the OUhierarchy, and DNs to application objects, application family objectsand application group objects. They exist as LDAP object classesgroupOfUniqueNames and pae-UserGroup, stored under ou=Groups, andcontain, for example:

cn (Name)

Display Name

DNs of users who are members of the group

DNs of applications

pae-NameValuePairs—strings associated with this group

Application groups are groups of DNs pointing to applications in theapplication Directory Information Tree (an LDAP term referring to anarea within the LDAP directory), and may well point to anotherapplication group. They exist as LDAP object classes groupOfUniqueNamesand pae-ApplicationGroup, stored under ou=Groups, and contain, forexample:

cn (Name)

Display Name

DNs of applications

pae-NameValuePairs—strings associated with this group

Application objects are chosen based on the policy as held in theapplication family object. A “policy” is a set of rules that describewhich application object a particular application family object resolvesto at a particular point in time and at a particular point of use. Thispolicy may be “partially resolved” by the entitlements support of theAWS Web Services (as some parts refer to information that is only knownat that point, such as the method of authentication to the AWS), andpartially resolved by an AWS Node Manager based on information availablelocally to the managed workstation (such as packages already installedon the computer).

Policy is stored in the application family object as a goal ofentitlements resolution is to resolve an application family object to anapplication object for that user at that time. While it is possible toassign an application object directly to a user object in theconfiguration store, this may not be advisable as it may result in thesystem attempting to do something inappropriate (e.g., installing thewrong application on the wrong operating system), or attempting toprovide a remote application when there is no network connectivity, etc.

Examples of policy as expressed for local applications are:

-   -   If one is already installed, use that    -   Always use this one    -   If nothing else is installed, use this one    -   Use this one for this particular operating system    -   Use this one in these particular circumstances    -   Only install this particular one if this other application class        is not installed    -   For this particular user community, use this remote application    -   Use this particular remote application if an older version is        installed locally

The nature of expressing circumstances is through the use of thename-value tuples (e.g., name-value pairs). These name-value pairs areavailable in the query language, and can form part of the expressions.In addition, the environment and user name-value pairs are available tothe expression in the form of expansion variables (that take the form$(Variable)). Finally, some de-facto variables are available, mostnotably, the key of the application family object in question, andenvironmental information, such as whether a network connection ispresent, the IP address and DNS name of the computer, etc.

Each “rule” of the policy exists in an ordered list. This list is thenevaluated, in order, with each successful evaluation (i.e., the policyreturning a value) resulting in that value being pushed onto the back ofa vector which represents the result of processing the policy for thatapplication family object.

Examples using the above policies are as follows.

Example: If one is already installed, use that. Otherwise, applicationis not available.

(applicationClass = ‘$(WSID)’ AND installedApplicationInstance IS NOTNULL)Example: Always use this one.(wsid=‘cn=1,0,0,1,ou=MyApp’)Example: If nothing else is installed, use this one, otherwise use theone that is installed.

(applicationClass = ‘$(WSID)’ AND installedApplicationInstance IS NOTNULL) (wsid = ‘cn=1,0,0,1,ou=MyApp’)Example: Use this one for this particular operating system.

(applicationClass = ‘$(WSID)’ AND ( exists i:(nameValuePairs[i].name=‘_OS’ AND nameValuePairs[i].value=‘$(OS)’) ) )

A policy has three flavors—LOCAL, REMOTE, ALL/BOTH. The three flavorsare because there are two different scenarios when a user can accessworkspace:

-   -   From a managed workstation that can execute local applications    -   From an unmanaged workstation that can only access remote        applications        Policy is structured as follows:

PRIORITY:TYPE:USERS:RULE

where:

-   -   PRIORITY: the order in which the rule is executed—each item is        numbered    -   TYPE: one of REMOTE, LOCAL or ALL (some implementations use        “BOTH”)    -   USERS: applicable users, groups or OUs—this indicates to which        users this policy applies    -   RULE: text of the rule, as above.

Once an application family object has been resolved to an applicationobject, if the application object represents a local application, thenpackage objects must then also be determined and associated with theapplication because packages are the ultimate item that gets physicallyinstalled on the computer to enable the application to function. Onereason for the existence of package containers is that, when usingWindows Installer Packages (MSIs), it is necessary to remove using thepath to the old MSI, and install/upgrade using the path to the new MSI.As a result, the locations of both need to be available at the time ofan upgrade, so simply modifying an existing package object to point at anew MSI would not be sufficient. The package containers allowadministrators to group together the information needed for suchremoval.

Packages to be installed locally can be vendor supplied installationpackages that do not require any further modification or they can bepackages generated by the AWS. An example embodiment of the AWSpackaging mechanism splits an application package into three separateparts—SYSTEM (containing shared data that is common across the wholecomputer system), USER (containing information that is stored for eachuser), and WSM that contains scripts which can perform configurationtasks when certain events are triggered.

The AWS creates a package using a mechanism of capturing the state of asample access device (similar in nature to the access device that thepackage will eventually be installed on). This is not a run-time task,but an administrative task. The application is installed from its sourcemedia onto that same access device. The AWS then captures the state ofthe access device after the install as above has occurred, but appliesrules to decide which parts of that install can be classified as“SYSTEM” (i.e., applies to all users and does not require access to anyuser specific configuration areas on the access device), and which partscan be classified as “USER” (i.e., are user specific, and would need tobe added to any user specific configuration areas on an access devicebefore a user was able to properly use that application on that accessdevice). The system contains a default set of rules that may be providedto the Node Manager by the AWS Manager Workbench at the time the packageis created, but they can be adjusted if required.

This package can then be adjusted using tools available in the system(the Workbench), and can have scripts added to the package that aretriggered by the system when certain events occur (see FIGS. 18-20described below). Also, this package can be digitally signed by thesystem to prevent tampering before being delivered to target accessdevices.

Once adjusted, this package can then be placed in the AWS packagerepository—this process also involves configuration data relevant to thepackage being added to the AWS's configuration database (usually, areplicated LDAP directory).

As mentioned one of the features offered by the AWS applicationabstraction mechanism is that associations between the concepts ofapplications and users are actually between users and applicationfamilies.

FIG. 14 is an example screen display of a user interface provided by anexample AWS Web Services for configuring application family objects inan example configuration repository. It shows a view of an applicationfamily 1401 called “Office” 1402 being configured, and two policy blocks1404 and 1405 (sets of rules) that select a different application basedin this instance on username. In this case, user “test1” is assigned alocal application 1407 for Microsoft Office 2003 and user “test2” isassigned a remote application 1408 for Microsoft Office 2003.

Administrators can associate application family objects with users,groups etc. by using direct manipulation techniques (such as drag anddrop). FIG. 15 is an example screen display of a user interface providedby an example AWS Web Services for associating application objects andapplication families with users in an example configuration repository.In FIG. 15, an application object 1504 “GAIM for Windows” is beginassigned (associated with) user “test1” 3601. Application families canbe assigned in a similar manner. One can observe that the user “test1”1501 is a member of a user folder 1505 “people” but is not part of anygroups 1502. Hyperlinks 1506 provide easy access to other parts of thedata model that may be configured.

In one embodiment of the AWS, the association between the user andapplication family is stored in LDAP as a DN link as an attribute of theuser object in LDAP pointing to the Application object in LDAP. Wheregroups are used, the groups act as a form of intersection between thetwo objects—that is, they contain a list of DNs to the applicationobjects, and a list of DNs to the users who are members of the group.

FIG. 16 is an example flow diagram of an administration process providedby an example AWS Web Services for configuring an application object inan example configuration repository. Typically, an IT administratorwould carry out this steps. In step 1602, the administrator creates apackage container object if needed or uses a default provided with thesystem. In step 1602, the administrator creates a package object withall of the attributes for installation, upgrading, and removal of thecorresponding application. For example, such attributes may include apath to physical files, the type of package, status codes, or otherinformation. FIG. 17 is an example screen display that shows variousproperties that can be set for a package. In step 1603, theadministrator designates a new or existing application object, and instep 1604 associates it with the created/reused package object. In step1605, the administrator designates a new or existing application familyobject, and in step 1606 associates it with the designated applicationobject. In step 1607, the administrator adjusts policy blocks in theapplication family object to indicate when to use the newly associatedapplication object.

Configuration and personalization of applications either on the managedworkstation (i.e., local applications) or on application servers thatare participating in the system (e.g., Terminal Servers) occurs whenspecific events are generated on these computers. In one embodiment ofthe AWS, a Node Manager component of the (see, for example, Node Manager410 in FIG. 4) is a daemon process that resides on these computers andthat causes the execution of scripts associated with applicationpackages in response to certain defined system events (triggers). TheNode Manager daemon is an asynchronous message based component that canrespond and deliver events that can execute scripts either with elevatedprivileges (“root” or “administrator” privileges), or in the context ofany user currently logged into the computer. In FIG. 4, the eventruntime and script object support 411 is responsible for the event-basedscript system.

In order for customization to occur, an administrator needs to havedefined scripts and associated them with the application object ofinterest. Adding scripts to a package to be triggered upon events can beperformed using the AWS Manager Workbench. As described above, eachpackage has three parts (called features), which include the SYSTEM,USER and WSM features. WSM stands for workspace Manager, and is theportion into which scripts are stored. In FIG. 17, package information1701 contains the three portions 1704. The scripts property 1702 isshowing one script defined for a CONFIG event 1703.

FIG. 18 is an example screen display that illustrates the assignment ofa script to a package based upon a pre-defined script events. A menu ofevents 1801 is displayed for adding a single script to the package.

Table 1 below includes explanations for example events which can triggerthe execution of scripts associated with an application package:

TABLE 1 SCRIPT_EVENT_MACHINESTART // The Node Manager service hasstarted SCRIPT_EVENT_CONNECTNETWORK // A network connect SENS event hasbeen received SCRIPT_EVENT_DISCONNECTNETWORK // A network disconnectSENS event has been received SCRIPT_EVENT_LOGON // A logon SENS eventhas been received. This shouldn't // be used for applicationconfiguration, but rather system // processing or notifications to bedone on logon SCRIPT_EVENT_PRESHELLLOGON // A user has logged on andprofile/session is available, but the shell is not yet started - usethis to configure email systems and shell related settingsSCRIPT_EVENT_CONFIG // Main configure the package - this usually happensafter the shell // has started for apps that are entitled & installed,and // after the final user install for apps that are installed // afterthe user has logged on. Also triggered for all // installed apps when an“Update my computer” or forced // update occurs. SCRIPT_EVENT_LOGOFF //A user has logged off SCRIPT_EVENT_PRESYSTEMINSTALL // System featuresare about to be installed SCRIPT_EVENT_POSTSYSTEMINSTALL // Systemfeatures have been successfully installed SCRIPT_EVENT_PREUSERINSTALL //User features are about to be installed SCRIPT_EVENT_POSTUSERINSTALL //User features have been successfully installed. Note that // if thisscript fails, then the User features will be removedSCRIPT_EVENT_PRESYSTEMUPGRADE // System features are about to beupgraded (repaired) SCRIPT_EVENT_POSTSYSTEMUPGRADE // System featureshave been successfully upgraded (repaired) SCRIPT_EVENT_PREUSERUPGRADE// User features are about to be upgraded (repaired)SCRIPT_EVENT_POSTUSERUPGRADE // User features have been successfullyupgraded (repaired) SCRIPT_EVENT_PRESYSTEMREMOVAL // System features areabout to be removed (for major upgrade) SCRIPT_EVENT_POSTSYSTEMREMOVAL// System features have been successfully removed (for major upgrade)SCRIPT_EVENT_PREUSERREMOVAL // User features are about to be removed(for major upgrade) SCRIPT_EVENT_POSTUSERREMOVAL // User features havebeen successfully removed (for major upgrade)SCRIPT_EVENT_STARTSCREENSAVER SCRIPT_EVENT_STOPSCREENSAVERSCRIPT_EVENT_ACPOWER SCRIPT_EVENT_BATTERYPOWER SCRIPT_EVENT_BATTERYLOWSCRIPT_EVENT_SHUTDOWN

Note that scripts have access to all of the tuples (e.g., name-valuepairs) configured for that package in the configuration repository, aswell as tuples for all applications already installed on the localcomputer (so that application level settings can be shared), as well astuples configured for that user and associated groups. (There are anumber of different precedent orders that can be applied when mergingthe set of tuples to deal with tuples that have the same name). Thesetuples typically exist as a multi-valued string attribute on each objectin the configuration repository.

By nature of being able to manage, configure and supply configurationinformation via these tuples stored in the AWS configuration repository,the AWS as a whole is able to deliver, manage, configure and personalizeapplications for users. For example, a script that responds to changesin the network state could change the default document location of aword processor to the user's home directory on a network server if thenetwork is present, and to a local directory on the computer when thenetwork is no longer present.

FIG. 19 is an example screen display of a script used to configureapplications. It illustrates a script being edited by anadministrator—in this instance, it is a CONFIG script (the most commonlyused script event), as can be observed from the name of the script 1901and pathname 1904. This screen display also demonstrates the use of anAWS script object to access tuples 1903 defined for the user. The use oftuples by scripts is described with reference to FIGS. 34 and 35.

Of note, the scripts execute in an environment that allows full remotedebugging of their execution, even though they are asynchronouslytriggered. FIG. 20 is an example screen display of a debugger of anexample Application Workspace System used to debug a script. Inaddition, the AWS supports an Application Programming Interface (“API”)for script object capabilities.

The AWS Node Manager implements an asynchronous event handler forinvoking appropriate application scripts when an event is triggered.Events can be system triggered or defined by the AWS. In one embodiment,events are triggered by four distinct mechanisms:

-   -   WMI—“Windows Management Instrumentation” which is a Windows        Mechanism that allows processes to subscribe to particular        Windows events. The AWS Node Manager subscribes to ones        pertaining to (but not limited to) process start/stop and print        job creation.    -   SENS—“System Event Notification Services” which is a Windows        mechanism for dealing with processes that need to react to        specific hardware or session events. The AWS Node Manager        subscribes to logon, logoff, shell start and power state        changes.    -   Process injected events—AWS Node Manager ships with a component        called WSUTIL that when executed will inject an event into the        executing Node Manager process. For example, WSUTIL can be        scheduled with the Windows scheduler to trigger an event at a        specific time on a specific date.    -   WSSM—This term refers to the portion of the AWS Node Manager        which runs in USER space. For example, in one embodiment the        WSSM runs as the Node Manager Message Support 421 in FIG. 4.        This is called out as a separate event creation component,        because, by the very nature of it being executed (as it is        configured into the Windows registry as a replacement for the        Windows shell), the script knows that an actual logon and shell        start has been requested by Windows. As a result, the script can        trigger events into the executing Node Manager process. For        example, the entitlements resolution process is actually        triggered by Windows starting WSSM (and hence WSSM knowing that        a user logon has occurred).        Other types of events can be similarly integrated.

Each time one of these external events occurs, an external event handler(e.g., a WMI subscriber, a SENS subscriber etc.) calls the Node Managerdaemon process (either through an internal API or by invoking WSUTIL)with the name of the event (see SCRIPT_EVENT_XXX definitions), specifiesthe target queue/service name as the script service (“ScriptManager”with ID “{E8F61878-8DA6-494c-829D-017773AF1F05}”), and builds aparameter block if appropriate containing parameters for the event(e.g., a network connect event may indicate which interface wasconnected at which speed).

FIG. 21 is an example flow diagram of an event handling and scriptinvocation mechanism provided by the client side of an exampleApplication Workspace System. In an example embodiment, this handler isinvoked as a part of the ScriptManager service. In step 2101, thehandler determines the event, a target service, and the variousparameters stored in the created parameter block. In step 2102, if auser identification is supplied, the handler determines whatapplications have been installed for that user. The purpose of thischeck is to provide the Node Manager from invoking scripts forapplications present on the computer but not entitled to the user. Insteps 2103-2106, the handler performs a loop to retrieve the scriptobjects defined for each application for the detected event.Specifically, in step 2103, the handler starts the loop relative to thefirst application. In step 2104, the handler looks to see if there is acurrent application to process and, if so, continues in step 2105,otherwise exits the loop to step 2107. In step 2105, the handlerretrieves the script objects defined for the designated events.

In particular, the script name for a package that is part of anapplication is stored in the installed database (on the managedcomputing device), as it was an attribute of the package object that ledto the installation of that package. Each script is stored in a subdirectory named according to the external event type. For example, if apackage had a script name of “TEST”, and defined a script forSTARTSCREENSAVER and STOPSCREENSAVER, then the actual files on the diskwould look like:

C:\ProgramFiles\Propero\workSpace\Scripts\STARTSCREENSAVER\TEST.VBSC:\ProgramFiles\Propero\workSpace\Scripts\STOPSCREENSAVER\TEST.VBS

By querying the installed database, the Node Manager can build a list ofscript names to execute. By examining the name of the event as passed toit, it can identify the directory in which to find the scripts. Thus itis able to execute the correct scripts for the event. If no username ispassed in, then the Node Manager by default will execute all the scriptsfor that event.

In step 2106, the handler obtains the relevant name-value tuples thatcorrespond to the applications and their associated family objects andassociates them as appropriate with the scripts. The handler thenreturns to the beginning of the loop in step 2104. In step 2107, whenall applications having scripts triggered by the current event have beenhandled, then the handler obtains name-value tuples for users and forthe user's groups. Finally, in step 2108, the accumulated script objectsare executed.

In order to be able to provide personalized customization for theapplications, each script needs to have access to the correct tuple setfor the user, for that application. Therefore, for each script that isexecuted, a set of tuples (also referred to as NVPs, or Name ValuePairs) is compiled that the script can access.

The installed database records all the tuples associated with users,application objects (and the associated application family object thatresolved to that application object) and package objects that NodeManager has installed. These are stored in the installed database withtheir owning object, allowing the Node Manager to build different setsof tuples at different times. (These sets are refreshed every time NodeManager reads an entitlements document thus allowing new configurationvalues that administrators may set in the configuration repository to beused even if the application/package has already been installed.)

Therefore, whenever a script needs to be executed, NM builds a set oftuples from the installed database that is correct for that package. Theprecedence order of building this set is as follows:

-   -   1. User (this will includes ones from the user's groups)    -   2. Package (this particular package for which the script is        about to be executed)    -   3. Applications (all applications that have been configured on        this computer for this user)        This set is available to the script as part of an AWS script        object.

FIG. 22 is an example screen display illustrating user level name valuetuples usable by AWS scripts. In FIG. 22, multiple name-value pairs 2204have been associated with the user “test1” 2202. FIG. 23 is an examplescreen display illustrating application level name value tuples usableby AWS scripts. Name-value pairs 2305 contain one value“jabberresource=GAIM” 2305. Note that other details regardingconfiguring this application are also present as parameters 2302-2304.

Appendix C, incorporated herein by reference in its entirety, providesan example Visual Basic script that configures GAIM Instant Messagingfor each user. This is the script used in FIGS. 8A-8F and 9A-9L. Thescript accesses tuples to write configuration files for GAIM. Theper-user tuples are “jabberid, jabberserver, jabberalias,jabberpassword, jabberconfroom, jabberconfserver.” The application leveltuple in this instance is “jabberresource,” (Note that for the sake ofthis example, plain credentials have been used. Normally, these would beencrypted). These are the same tuples shown in FIGS. 23 and 22.

Referring back to FIG. 6, once all of the various administration ofapplications and users has taken place and the entitlements have beenstored in the configuration repository for one or more users,applications, application families, etc., it is possible for the AWS toperform its automatic configuration and personalization when therelevant events are on a managed computing device. Steps 602-604overview what happens when a logon event triggers, thereby triggeringthe WSUTIL script described above. Specifically, upon receiving noticethat a user has logged on, the AWS performs entitlements resolution tofigure out which applications to install/upgrade, automaticallyinstalls/upgrades certain applications, and presents a user interface tothe user for further installation and/or upgrade.

Entitlements resolution is the overall decision process that takesinformation stored in the AWS configuration repository and decides whichapplications a user is allowed to use, over which delivery mechanisms,and at the point of use. Thus, entitlements resolution is central toproviding a virtual workspace. The AWS resolves the application familiesthat are assigned to a user into the actual applications that are to beused at the point in time they are being requested, whether local orremote.

In one embodiment, entitlements resolution is performed by an AWS NodeManager querying the Entitlements Support and Information Servicescomponents for entitlement information and then performing a rules-basedset of actions as described above in the discussion regarding policy.

Entitlements resolution is typically performed whenever a new user logsinto the system as described with reference to FIG. 6, however,refreshing this information can be done at any time. For example, anevent that refreshes the user's entitlements and associated informationcan be triggered from scripts, the command line, or from menu optionswithin the user interface of an AWS Node Manager.

FIG. 24 is an example overview flow diagram of processing performed bythe client side of an example Application Workspace System when a logonevent is detected on a managed computing device. As mentioned, theprocessing is typically performed by a Node Manager component of an AWSManager executing on a managed computing device. FIGS. 25-31 describethe details of the steps illustrated in FIG. 24. Specifically, in step2401, the Node Manager determines a user ID, typically from the loginevent. In step 2402, the Node Manager retrieves configurationinformation to determine the location of the information (directory)services and entitlements services. In step 2403, the Node Managerrequests authentication of the indicated user ID from the determineddirectory service. In step 2404, if the user authenticates, then theprocessing continues in step 2405, otherwise, the Node Manger typicallyreturns control to the native UI, for example the Windows desktop. Instep 2405, the Node Manager requests entitlements information from thedirectory (information) services for the designated user and point ofaccess. The process for generating this information on the server sideis described further below with respect to FIG. 25. In step 2406, theNode Manager requests the AWS entitlements support of the AWS WebServices to generate a partially resolved policy for the remoteresources. The steps for generating a partially resolved policy aredescribed further below with respect to FIG. 26. In step 2407, the NodeManager resolves the (received) entitlements information relative tolocal, remote, and combined resources accounting for the receivedpartially resolved policy. The details of this process are describedfurther with respect to FIG. 27. A results vector of potentiallyavailable application objects is available at this time. In step 2408,the Node Manager adjusts the initial indication of potentially availableapplication objects. The details of this process are described furtherwith respect to FIG. 28. In step 2409, the Node Manager initiallyprocesses each potentially available application object to eliminateexclusions, account for dependencies, and to automatically configureapplications that result in mandatory installation. The details of thisprocess are described further with respect to FIGS. 29A-29B. In step2410, the available applications are presented as options fordownloading and configuring if desired. Any user selections of suchoptions potentially result in the Node Manager installing/upgrading anapplication. In step 2411, the routine processes the user selections,completes, and control is returned to the native operating system.

FIG. 25 is an example flow diagram of processing performed by an exampleweb services component of an example Application Workspace System toretrieve entitlements information from a configuration repository. Theentitlements information is typically stored as an XML document. Asmentioned, the Node Manager may request the entitlements informationfrom a directory (information) services component of the AWS Web server,such as information services 313, through entitlement support 311 inFIG. 3. The information service retrieves the entitlements informationfrom the configuration repository and returns it via an XML document.Note that other forms of recording the information could also besupported.

Specifically, in step 2501, the service determines the designated user,either from the request itself (via optional parameter <UID>) orimplicitly from an authentication request. In step 2502, the servicedetermines which user the user ID corresponds to (the designated user)and retrieves the groups the user is a member of from the configurationrepository. In step 2503, the service determines the name-value tuplesthat correspond to the designated user and the user's groups. In step2504, the service determines which application family objects have beenassociated with the designated user or the designated user's groups. Instep 2505, the service determines all of the possible applicationobjects that could be available to the designated user by looking at theapplication object associations of each determined application familyobject. In step 2506, the service determines all of the possible packageobjects and package object containers that correspond to the determinedapplication objects that are local. In step 2507, the service populatesan output report, here an XML “entitlements document” with all of thedetermined and retrieved information from the configuration repository.In step 2508, the output report is returned to the request, and theprocessing completes.

Thus, after processing, in the example embodiment, the informationstored in the XML entitlements document includes:

-   -   User name, and any other user attributes, and tuples associate        with the user;    -   Groups the user is a member of, and tuples associated with those        groups;    -   All Application Family Objects the user is entitled to (whether        by a direct assignment, or via a group membership), with their        associated attributes including tuples.    -   All Application Objects that could possibly be resolved to by        the Application Family Objects above, with their associated        attributes including tuples.    -   All possible Package Objects (and Package Container Objects)        that may be used by the Application Objects above, with their        associated attributes including tuples.    -   Confidential information is preferably encrypted.

Appendix A, incorporated herein by reference in its entirety, is anexample entitlements document stored as an XML document.

FIG. 26 is an example flow diagram of processing performed by an exampleweb services component of an example Application Workspace System toresolve entitlements for remote applications. This processing may beperformed, for example, by the entitlements support 311 of the AWS WebServices 310 in FIG. 3. This process is sometimes referred to asbuilding a partially resolved policy document and was invoked, forexample, in step 2406 in FIG. 24. Partially resolved policy documentsare produced for remote applications by the AWS Web Services, and forlocal applications by an AWS client process such as the Node Manager. Inthe described embodiment, the Node Manager subsequently puts the twopartially resolved policy results together to fully resolve the policy(i.e., evaluate the rules in the entitlements document). Partiallyresolved policy for remote applications is retrieved from the AWS WebServices as there are certain aspects of remote policy that use what istermed a “profile” to choose the correct application object. A profilemay depend on information such as the IP address of the caller, wherethe entitlements service is physically, time of day etc. These valuesmay be subsequently used in the REMOTE policy statements beingevaluated. For example, a particular profile may only be active duringworking hours, and if outside working hours, the service will not returnthat application object in the partially resolved policy document.

Specifically, in step 2601, the service determines the designatedrequester (typically a user ID associated with the web browser interfaceor the AWS Manager). In step 2602, the service requires the informationservices component (which interfaces to the configuration repository) toretrieve information specific to the requestor. In step 2603, theservice queries the information services component to retrieve a profilebased upon a set of current attributes, as described above. In step2604, the service matches the retrieve requestor information to theretrieved profile to make sure the profile is applicable. At this point,in step 2605, the entitlements support sends a request to theInformation Services (e.g., the LDAP support) to obtain an entitlementsdocument (as described with reference to FIG. 25) based upon the user IDassociated with the designated requestor. When the entitlements documentis received, then in step 2606, the service resolves all of the policyrules for “REMOTE” and for “ALL” or “BOTH,” using the retrieved profile.In step 2607, it then returns the entitlements document with answers tothe rules it resolved to the requestor.

Note that although many of these service routines are shown in the flowdiagrams as sequential steps, it is to be understood that many of theseservices are written as asynchronous event handlers that processrequests and data as they arrive. Equivalent synchronous flows arecorrespondingly incorporated.

At this stage, the entitlements document retrieved from the AWSInformation Services contains a list of application family objects thathave been assigned to the user or via group memberships, and thepartially resolved policy document from the entitlements supportcontains a partial resolution of the policies contained in theentitlements document. The next step is for the AWS Node Manager toresolve these entitlements into vectors of possible application objects.The reason that vectors are used, rather than single items, is toprovide alternatives if a user does not select the most appropriateapplication (e.g., the one at the beginning of the vector). If anotherapplication is available, then the Node Manager will use it instead. Forexample, if a local install of an application is not desired, and aremote one is available, then the Node Manager will make available theremote application.

FIGS. 27A and 27B are an example flow diagram of processing performed byan example client component of an example Application Workspace Systemto resolve entitlements for a managed computing device. This is theprocessing that puts together the prior partially resolved policy withNode Manager resolved policy, and may be performed, for example by theNode Manager component of an AWS Manager. It may be invoked, forexample, from step 2407 of FIG. 24.

In summary, the routine performs a loop on each application familyobject found in the entitlements document and evaluates eachcorresponding policy resolving the results where appropriate with theinformation returned by the partially resolved policy document.Specifically, in step 2701, the routine processes each applicationfamily object starting with the first. In step 2702, the routinedetermines whether there are more application family objects to process,and, if so, continues in step 2704, else continues in step 2703. In step2704, the routine determines whether there are more policy statements toprocess, and, if so, continues in step 2705, else returns to the top ofthe outer loop to obtain the next application family object to process.In step 2705, the routine evaluates the next policy statement inpriority order. In step 2706, if the policy statement is tagged as“LOCAL”, then the routine continues in step 2712. If in 2706, the policyis not tagged as “LOCAL,” then in step 2707, then determines whether thepolicy statement is tagged “ALL” (or “BOTH” in some versions). If so,then the routine continues in step 2709, otherwise continues in step2708. In step 2708, the policy statement is tagged “REMOTE,” and theroutine looks up the corresponding result in the partially resolvedpolicy document (to make sure there is a value), pushes an indicator tothe resulting application object onto the application object vector, andreturns to process the next policy statement in step 2704.

In step 2709, the routine has determined that the policy statement istagged “ALL” or “BOTH.” It evaluates the policy and then in step 2710compares the resulting value with the value returned by the remoteresults communicated in the partially resolved policy document. In step2711, if the results match, then the routine pushes an indicator to theresulting application object onto the application object vector, andreturns to process the next policy statement in step 2704.

In step 2712, the has determined that the policy statement is tagged“LOCAL.” It evaluates the policy and then in step 2713 determineswhether the evaluation resulted in an application object (it succeeded).If so, in step 2714, the routine pushes an indicator of the resultingapplication object onto the application object vector associated withthe current application family object, and returns to process the nextpolicy statement in step 2704.

Once all of the entitled application family objects have been processedand all of the respective policies, then the routine returns a resultvector (step 2703) with application object vectors for each applicationfamily object.

Once the results vector is completed, then, per step 2408, the NodeManager adjusts each application object vector to account fordependencies and exclusions. FIG. 28 is an example flow diagram of aroutine to adjust an application object vector. It is performed on eachof the application object vectors in the result vector (not shown). Inone example embodiment, this routine is also performed by the NodeManager. In step 2801, the routine starts a loop on each applicationobject in the vector starting with the first. In step 2802, the routinedetermines whether there are more objects to process, and, if so,continues in step 2804, otherwise in step 2803 returns the adjustedapplication object vector and then returns. In step 2804, the routinedetermines whether the current application object being examined is alocal application and, if so, continues in step 2805, otherwise skipsthe object and returns to the beginning of the loop in step 2802. Thisis because the exclusions and dependencies are applicable for localapplications, not for remote applications. In step 2805, the routinedetermines whether the application object lists an exclusion on one ormore application objects and the excluded object is present in thesystem registry. If so, then in step 2806 the routine removes theapplication object from the result vector because it is incompatiblewith an already installed application. The routine then continues instep 2807.

To perform this determination, the Node Manager maintains what is termedan “installed database” on the managed computing system (commonly storedin the Windows Registry) in which it records the keys of all packageobjects and application objects installed on the computer. This databaseis partitioned into the SYSTEM part, which records which actionsoccurred system wide on the computing system, and the USER part, whichrecords which actions occurred for that user. The exclusion check ismade against the SYSTEM part of the database. In other words, if thecomputing system has had an application installed on it that a potentialapplication object lists as an exclusion, then this potentialapplication object (potential in that it exists in the set of vectorsabove) is then removed from that vector. The purpose of this exercise isto prevent incompatible applications being installed on the sameworkstation which may occur if two or more users share a workstation,and different applications are assigned to them in the configurationrepository.

In step 2807, the routine checks if the current application object beingexamined has a dependency on one or more additional application objects.If not, the routine continues back to the beginning of the loop in step2802 to examine the next object. Otherwise, then in step 2808, each ofthe dependent application objects is added to the vector (or a newvector added for each and added to the application object vector).

After the results vector is has been adjusted, then, per step 2409, theNode Manager processes each application object to determined whether toqueue applications for installation or upgrade. This involves using theinstalled database on the computing device as mentioned above. FIGS.29A-29B are an example flow diagram of processing performed by anexample client component of an example Application Workspace System toprocess application objects in preparation of installation and upgrade.In one example embodiment, this processing is also performed by the NodeManager.

In summary, the Node Manager iterates through all of the package objectsreferenced by each application object, and checks in the installeddatabase to determine whether some or all parts of packages associatedwith the possible application objects have already been installed andare correct. The Node Manager then decides whether an application needsto be installed or updated and marks it according.

Specifically, in step 2901, the routine processes each applicationobject in each application object vector starting with the first. Instep 2902, the routine determines whether it is done. If there are nomore objects to process, then the routine continues in step 2913 toreturn the application object result vector and then starts a new loop(steps 2914-2919) to process any applications that must be installed andwill cause a reboot. If there are more objects to process, then in step2903, the routine determines whether an “Install_Always” attribute hasbeen set, and if so continues in step 2912 (to require an upgrade andpotentially mark as mandatory, including identifying packages that areno longer required), otherwise continues in step 2904. In step 2904, theroutine determines whether both the SYSTEM and the USER parts have beeninstalled. This check involves checking that the versions of the packageobjects match as well as that all of the packages have been installed.This includes identifying packages that are no longer required. If instep 2905 everything matches, then the application object is consideredto have been already installed correctly. Then in step 2906, if thisapplication object is at the top of its containing vector, the wholevector is removed from the set in step 2907 and the routines skips tothe next application object vector in step 2902. Otherwise, in step2908, the application object is removed from the vector (it isn't thetop object) the remainder of the vector is processed in step 2902.

In step 2905, the check for a match could fail either because nocorresponding application has been installed, or some portion didn'tmatch. Therefore, in step 2909, the routine checks to determine whethernothing was installed. If true, then in step 2910 the application objectis marked as available for installation (which is used for UI hints inthe workspace presentation) and the remainder of the vector is processedin step 2902. If false (the application was previously installed and thepackages and values don't match), then the routine continues in step2911 to determine whether the parts that are present or the packagesrequire an upgrade. If so, the application object is marked for UPGRADEin step 2912, and, if at the beginning (top) of the vector, it is markedalso as MANDATORY. The routine then skips to the next applicationobject.

Note that this process of deciding what needs to be done is primarilyperformed to filter out which application objects need no action—thisprocess is repeated later on when applications and packages are actuallyinstalled/upgraded/removed.

In steps 2914-2919, the Node Manager then scans all of the applicationobjects at the top of each vector in the set (step 2914) to see if anyhave both the mandatory attribute set and also have a reboot attributeset (step 2915). The reboot attribute may be used as a UI indicator towarn the user that this application may require a reboot afterinstallation, but if this attribute is present in combination with themandatory attribute, then in step 2919 the routines causes theseapplications to be installed and the system rebooted before anythingelse happens. If the shell (as in the operating system user interfacesuch as Windows Explorer) has not been started yet, it is not started atall if the Node Manage is configured with the“DontShowShellIfRebootRequired” flag is set. This prevents user activityas the machine will be rebooted after these mandatory operations havecompleted. This approach is commonly used for critical application orsecurity fixes. After the machine reboots, the whole entitlementsresolution process is restarted as the user logs on.

In step 2916 (by the time the Node Manager arrives at this step again)then scans all of the application objects at the top of each vector inthe set to see if any have the mandatory attribute set. Those that doare queued for installation processing immediately. Immediate processingcan be achieved as the Node Manager is an asynchronous queue basedsystem. In step 2917, the Node Manager then scans all of the applicationobjects at the top of each vector in the set to see if any are remoteapplication objects. Any found are queued for remote applicationprocessing immediately. In step 2918, the resulting application objectvectors are returned for further processing.

In step 2410 of FIG. 24, the remaining application objects at the top ofeach vector are presented to the user. FIG. 30 is an example screendisplay of a virtual workspace presented to a user after the automatedconfiguration processing performed by an example client component of anexample Application Workspace System. In FIG. 30, a remote application3003 has been processed (successfully—with a green tick 3004), and twoother applications 3005 and 3006 are available to the user. Theattributes “available for installation” or “requiring upgrade” are usedto change the icons and/or text next the items in the dialog box. Theuser can choose to install the optional applications by selecting link3007, or can skip any further installation by selecting link 3008.

The Node Manager then continues processing the user selections in step2411 of FIG. 24. FIG. 31 is an example flow diagram of processingperformed by an example client component of an example ApplicationWorkspace System to process user selections to install or upgradeoptional applications. In step 3101, if the “Skip” option was selected,no application objects are marked as requested for install/upgrade andthe routine returns. If not (the “Install” option was selected), then instep 3102 any application objects that the user checked are marked asrequested (this is an attribute of the application object).

The routine then performs a loop to queue for installation/upgrade allrequested objects, or to install/upgrade alternatives if they areavailable applications (to which the user is entitled).

Specifically, in step 3103, the Node Manager searches each applicationobject vector in the set, starting with the first. In step 3104, ifthere are no more vectors to process then the routine is done;otherwise, it continues to examine the vector in step 3105. In step3105, if top application object has been marked as requested, then instep 3106 this application object is submitted for installationprocessing and the next vector is processed. On the other hand, if thetop application object has not been marked as requested, then in step3107, the Node Manager moves down the vector to see if any furtherapplication objects are available. Note that no further choices arepresented to the user—this technique is usually used to provide the userwith a remote application if the user chooses not to install a localapplication, or to ensure that an existing local application isupgraded, if required, if the user chooses not to install a differentlocal application. In step 3108, If the NM finds an alternateapplication object in the vector, and this application object is a localone marked requiring an upgrade, it is submitted for installationprocessing in step 3109. In step 3110, f the application object isremote, then it is submitted for remote application object processing instep 3111. The routine then continues back to step 3104 to process thenext vector.

At this point, the Node Manager will have resolved all the contents ofthe entitlements document, and will have submitted the relevantapplication objects for either installation processing, or for remoteapplication object processing (note that “installation processing”performs any steps involved in managing local installs, includingupgrades or removals). The Node Manager now deletes the set of vectors,as important state is now held in three places:

The queue of work for installation processing

The queue of work for remote application object processing

The installed database on the managed computing system.

As each application object is processed by installation processing, theinstalled database is updated. Remote application object processing doesnot update the installed database, as nothing is actually installed inthe database for remote applications.

The Node Manager then triggers the SCRIPT_EVENT_CONFIG script for eachapplication that is present in the installed database as installed forthat user.

As mentioned, applications for install or upgrade are queued becausethey can be processed asynchronously by a Node Manger of the AWS clientside processing. Installation processing is a term used forsynchronizing the state of the packages that comprise an applicationwith the desired state as described with the application objects andpackage objects that exist in the configuration repository. Installationprocessing can occur at multiple times.

As a result of installation processing, the Node Manager may determinewhether to install or upgrade an application. FIGS. 32A-32B are anexample flow diagram of the overall processing performed by an exampleclient component of an example Application Workspace System to installor upgrade an application instance. This process typically occurs when auser logs onto a managed workstation, for example, or through the webportal to a remote application executing on a Terminal Server (where itis installed on the Terminal Server). In summary, the Node Managercompares the state of the packages installed on the workstation and forthe user against the desired state, and adds/removes packages asappropriate. For an installation, the initial state will be that nothingis present—for upgrades, some existing state will be present.

The first part of the processing involves removing unwanted packages inan orderly fashion. The second part involves then upgrading the packagesand causing the appropriate events to occur so that the scripts can betriggered. The third part of the processing involves installing the“missing” packages, for example as occurs with either an install orupgrade.

Specifically, in step 3201, the routine looks to see if the USER portionof the packages associated with the application instance has beeninstalled. If not, it continues in step 3204. Otherwise, the routinebuilds a list of unwanted packages (step 3202), and removes theinstallation database information for the unwanted packages (step 3203).

In step 3204, the routine looks to see if the SYSTEM portion thepackages associated with the application instance has been installed. Ifnot, it continues in step 3209. Otherwise, the routine builds a list ofunwanted packages (step 3205); removes unwanted (SYSTEM and USER)packages triggering the PRE_SYSTEM_REMOVAL and POST_SYSTEM_REMOVALevents (step 3206); and builds a list of packages to upgrade (step3207). In step 3208, the routine upgrades (reinstalls) the SYSTEM andWSM features and triggers the PRE_SYSTEM_UPGRADE and POST_SYSTEM_UPGRADEevents.

In step 3209, the routine looks to see if the USER portion of theapplication instance has been installed. If not, it continues in step3212. Otherwise, routine builds a list of packages to upgrade (step3210) and upgrades (reinstalls) the USER feature, triggering thePRE_USER_UPGRADE and POST_USER_UPGRADE events. Note that the USERportion is installed after the SYSTEM and WSM portions.

In step 3212, the routines then adds missing (not yet installed) USERand SYSTEM packages as described below with respect to FIG. 33, runs theCONFIG scripts, and then completes processing.

FIG. 33 is an example flow diagram of processing performed to installmissing (new or replacement) packages on a managed computing device.“Features” are the package portions that correspond to items that needto be configured for everyone (the SYSTEM feature) or on a per userbasis (the USER feature). The WSM feature contains the event scripts. Asshown in FIG. 33, script events are performed when installing a package.

More specifically, the Node Manager engages in an orderly process toprocess application objects one at a time. For each object, NM firstchecks to see if any dependent application objects need to be processed,and if so, recursively processes these (step 3301).

After this, the NM checks to see if any new packages need to beinstalled. If they do, the packages are installed as follows:

-   -   The WSM feature is installed (for example, by invoking the        Windows Installer to install the WSM feature) (step 3306)    -   The PRE_SYSTEM_INSTALL script is invoked (step 3307)    -   The System feature is installed (as above, e.g., using the        Windows Installer) (step 3308)    -   The POST_SYSTEM INSTALL script is invoked (step 3309)    -   The PRE_USER_INSTALL script is invoked (step 3311)    -   The User feature is installed (as above e.g., using the Windows        Installer) (step 3312)    -   The POST_USER_INSTALL script is invoked (step 3313)

If any of these steps fail (not shown), portions may be backed out. Inparticular if the POST_USER_INSTALL script fails, then the Node Managertypically removes the User feature. The User feature usually containsthe shortcuts etc. of the local application—therefore this implies thatif the post install script fails, the application is not apparentlyavailable to the user.

The result of all of this processing is recorded in the installeddatabase on the computing device where the processing occurred. Forremovals, the relevant package records are removed. For upgrades, freshinformation is recorded. For installs, new records are added.

In addition to resolving entitlements, and installing applications andcustomizing them through the use of scripts, the AWS offers tools toremotely monitor data, state, and status of managed computing devicesand terminal servers. For example, the AWS Manager Workbench (see FIG.5) can also be used to view the configuration data stored by the NodeManager and possibly data from the native operating system as well asmonitor accesses to the computing system.

FIG. 34 is an example screen display of a portion of user configurationdata stored by example client component of an example ApplicationWorkspace System on a managed computing device. For example, theconfiguration data may be data stored by a Node Manager on a managedworkstation. In some embodiments, this data is actually stored in theWindows Registry on the computer. In FIG. 34, the application labeled“GAIM” has been installed as a SYSTEM feature 3401 which has not yetbeen installed for the user. FIG. 34 shows how the Node Manager storesapplication object and package object data as the Distinguished Names(ala LDAP) for the applications and packages.

A Node manager can also interact with the native operating system'sdatabase of installed applications. FIG. 35 is an example screen displayof the installed package set in a computing system repository of thesame computing device shown in FIG. 34. For packages that resulted in anMSI install, it is possible to see the same packages appearing in boththe Node Manager's database and the operating system's package database.

A Kernel Manager component, briefly described above, typically resideson the Terminal Server or on the managed computing device and can traceall the system calls it intercepts in order to achieve behaviormodification (it runs in “kernel” mode, which is privileged like adevice driver). A Node Manager can retrieve this trace information andsend it to the AWS Manger Workbench for further analysis. FIG. 36 is anexample screen display of remote monitoring of a managed computingsystem in an example Application Workspace System. File and registryaccesses can be seen in the trace window.

A trace is capable of showing:

File/Directory/Network share accesses

Registry Accesses

Process Start/Stop

Module Load/Unload

Device Driver Load/Unload

Network listens

Network connects

Network disconnects

Other accesses could be similarly incorporated.

One or more of the components of an example AWS can be implement on ageneral purpose computing system. FIG. 37 is an example block diagram ofa general purpose computer system for practicing embodiments ofcomponents of a Application Workspace System. The general purposecomputer system 3700 may comprise one or more server and/or clientcomputing systems and may span distributed locations. In addition, eachblock shown may represent one or more such blocks as appropriate to aspecific embodiment or may be combined with other blocks. Moreover, thevarious blocks of the Application Workspace System 3710 may physicallyreside on one or more machines, which use standard or proprietaryinterprocess communication mechanisms to communicate with each other.

In the embodiment shown, computer system 3700 comprises a computermemory (“memory”) 3701, (optionally) a display 3702, one or more CentralProcessing Unit (“CPU”) 3703, and (optionally) Input/Output devices3704. The Application Workspace System (“AWS”) 3710 is shown residing inmemory 3701. The components of the Application Workspace System 3710preferably execute on CPU 3703 and manage the generation and use of avirtual workspace and configured and personalized applications, asdescribed in previous figures. Other downloaded code 3730 andpotentially other data repositories 3720, also reside in the memory3710, and preferably execute on one or more CPU's 3703. In a typicalembodiment, the AWS 3710 includes one or more Node Managers 3711, one ormore configuration repositories 3712, one or more user interfaces 3713and session support 3714.

In an example embodiment, components of the AWS 3710 are implementedusing standard programming techniques. However, a range of programminglanguages known in the art may be employed for implementing such exampleembodiments, including representative implementations of variousprogramming language paradigms, including but not limited to,object-oriented (e.g., Java, C++, C#, Smalltalk), functional (e.g., ML,Lisp, Scheme, etc.), procedural (e.g., C, Pascal, Ada, Modula),scripting (e.g., Perl, Ruby, Python, etc.), etc. In addition, thevarious components of the illustrated embodiments may be implemented byway of a single monolithic executable running on a single CPU computersystem, or alternately decomposed using a variety of structuringtechniques known in the art, including but not limited to,multiprogramming, multithreading, client-server, or peer-to-peer,running on one or more computer systems each having one or more CPUs.

In addition, programming interfaces to the data stored as part of theAWS process can be available by standard means such as through C, C++,C#, and Java APIs; libraries for accessing files, databases, or otherdata repositories; through scripting languages such as XML; or throughWeb servers, FTP servers, or other types of servers providing access tostored data. The configuration repository 3713 may be implemented as oneor more database systems, file systems, LDAP servers or any other methodknown in the art for storing such information, or any combination of theabove. In addition, some operations may be implemented as storedprocedures, or methods attached to configuration “objects,” althoughother techniques are equally effective.

Also the example AWS 3710 may be implemented in a distributedenvironment that is comprised of multiple, even heterogeneous, computersystems and networks. For example, in one example embodiment shown belowin FIG. 38, the Node Manager 3711 and the configuration data repository3713 are all located in physically different computer systems. Inanother embodiment, various components of the AWS 3710 are hosted eachon a separate server machine and may be remotely located from the tableswhich are stored in the configuration data repository 3713. Differentconfigurations and locations of programs and data are contemplated foruse with techniques of described herein. A variety of distributedcomputing techniques are appropriate for implementing the components ofthe illustrated embodiments in a distributed manner including but notlimited to TCP/IP sockets, RPC, RMI, HTTP, DHTML, Web Services (XML-RPC,JAX-RPC, SOAP, etc.). Other variations are possible.

In example embodiments, these components may execute concurrently andasynchronously; thus the components may communicate using well-knownmessage passing techniques. Equivalent synchronous embodiments are alsosupported by an AWS implementation. Also, other steps could beimplemented for each routine, and in different orders, and in differentroutines, yet still achieve the functions of the AWS.

FIG. 38 is an example block diagram of detailed service side componentsof an example embodiment of a Application Workspace System and theirinteractions to provide the services described here. A client computingdevice that is unmanaged (not shown) communicates with the AWSApplication Servers 3820 through web server 3810. The client computingdevice 3801 communicates to with the AWS Application Servers 3820 toresolve entitlements, obtain applications to download onto a localdevice, etc. as described in detail above. In addition, the clientcomputing device 3801 (managed) communicates using web service calls forremote applications to Entitlements Portlet 3821 in order to obtaininformation regarding the remote applications and to run sessions, forexample, on Terminal Servers 3850. The session controller selects theappropriate Client Connection Manager 3825 based on the type of theremote application as stored in the configuration repository 3841, anduses that Client Connection Manager to choose an optimal server forprocessing a remote application. In addition that Client ConnectionManager provides all the necessary information to allow the SessionController to return DHTML and/or responses to Web Services calls thatenable the Client computing device 3801 to connect to the selectedserver processing the remote application. Commonly, although notrequired, the Client Connection Managers 3825 communicate via a loadbalancing message bus 3860 with Terminal Servers 3850 via listeningserver agents 3854 in order to choose an optimal server for processing aremote application. The load balancing message bus 3860 mechanism isfurther described with respect to FIG. 39.

The Entitlements Portlet 3821 communicates with Information Services3824 to obtain information from the configuration repository 3841 storedand managed by one or more LDAP Servers 3840. An AWS providedreplication mechanism that uses XSLT stylesheets to perform thereplication is described further below. This technique is used toreplicate the LDAP directories 3841 as needed by the system. TheEntitlements Portlet 3821 performs the entitlement resolution process asdescribed in detail above.

The client computing device 3801 uses AWS security services 3830 toimplement tunneling for secure connections to the applications serversand to perform remote application processing. The tunnel client alsoknown as the CAP, can be seen in the workstations on the diagram. Thecomponents of the security services 3830 also provide Kerberos securityservices to the system.

XSLT Based LDAP Synchronization

The XSLT based LDAP Synchronization technology (“XLDAPS”) allowssynchronization of LDAP data between directories of different typesusing a unique approach of a transformed replication changelog. NormallyLDAP replication is used to replicate directory data between twoidentical directory server implementations. In some environments,including the AWS described above, every data entryadded/deleted/modified in the LDAP is automatically replicated to theother directories. The XLDAPS technology uses XSLT transformation rulesto synchronize LDAP changes to different LDAP Directories which may havea different LDAP Schema and a different LDAP Directory Information Treestructure.

A transformation expressed in XSLT describes rules for transforming astandard replication log into a synchronization log. A transformationexpressed in XSLT is called a stylesheet. Appendix B is an example XSLTdocument as used in the AWS to perform LDAP replication.

The XLDAPS technology is implemented as an Directory Server plug-in andis used on an LDAP Directory Server (e.g., Sun Java Directory Server,IBM Tivoli Directory Server, Microsoft Active Directory etc.). It allowsadd/modify/delete operations performed on one LDAP Directory to besynchronized using corresponding operations on a completely differenttype of LDAP Directory.

For more information on LDAP—Lightweight Directory Access Protocol—IETFstandard—see RFC 3377 http://www.ietf.org/rfc/rfc3377.txt. For moreinformation on XSLT see XSLT—Extensible Style LanguageTransformations—W3 standard—see http://www.w3.org/TR/xslt.

Multiple instances of the Plugin can run each outputting a differentformat changelog (a changelog contains the datastream to be replicatedto the target directory server) each described by the XSL/XML definitionfiles. More about XSL is found at http://www.w3.org/Style/XSL/

Typical uses of this plugin include the generation of an OpenLDAP styleslurpd changelog to replicate LDAP changes to other LDAP serversincluding Microsoft Active Directory. The XSL stylesheet defines theslurpd replication changelog format and defines the mapping from LDAPattribute types to Active Directory attribute types. This means that theplugin does not need any knowledge of the slurpd changelog format or ofthe specific details of mapping LDAP attribute types to Active Directoryattribute types. Rather, the plugin can just invoke an XSLT processor toread and execute the transformations in order to produce the changelog.

This plugin can also be used to output a changelog for use by otherreplication and synchronization services such as for replicating changesto an RSA/Ace SecurID server or for producing an audit log in a specificformat.

The plugin is designed to work with Sun ONE Directory Server, but couldfairly easily be ported to work with IBM Directory Server on Intel orzSeries hardware. Currently it is supported on Intel Red Hat 7.3 Linuxworking with Sun One Directory Server 5.1.

This plugin is extensible. By using XSL as the changelog formattransformation mechanism, new replication requirements can be metwithout the need to make changes to the software. Adding a newreplication log, or changing the attribute mappings etc. can all be doneby modifying or creating a new XSL stylesheet and XML file definition.

In an example embodiment, the plugin is called libpaerep-plugin.so andis a re-entrant shared object library. It is configured in LDAP toautomatically start when the LDAP processes ns-slapd start.

When the plugin is started, it parses the XML and XSL files. If they arenot readable, or they contain syntax errors, the processing aborts andthe plugin will not initialize. Otherwise the XSL file is read todetermine the list of XSL parameters that are defined.

For efficiency, the XML and XSL files are only read and parsed atinitialization time. If the contents of the files are changed, it isnecessary to restart the LDAP processes ns-slapd. This is acceptable asthe contents of the XML and XSL files should rarely change.

Parameters configured in LDAP are passed to the plugin at startup todetermine the format of the changelog. They are defined in order asfollows:

-   -   XML Filename—The name of the XML file that contains any fixed        parameters needed by the specified XSL stylesheet.    -   XSL Filename—The name of the XSL stylesheet file that contains        the transformation definition for the XSLT processing to format        the changelog output.    -   Changelog Filename—The name of the changelog output file. If        this file doesn't exist it is created. Changes passed to the        XSLT processor may be appended to this file in a format        described by the XSL file after each LDAP add, modify and delete        operation.

The remaining parameters represent a list of LDAP attribute types forwhich values are always passed as parameters to the XSLT processingafter a modify operation. Usually after a modify, only the attributetype values that have been modified are passed together with certainfixed ones (see below).

The following LDAP entry shows an example plugin configuration used forActive Directory Replication.

dn: cn=Sample Active Directory Replication, cn=plugins, cn=config cn:Sample Active Directory Replication objectClass: top objectClass:nsSlapdPlugin objectClass: extensibleObject nsslapd-pluginarg0:/opt/Propero/properDirectory/ad_changelog.xml nsslapd-pluginarg1:/opt/Propero/properDirectory/ad_changelog.xsl nsslapd-pluginarg2:/usr/iplanet/servers/slapd-m49/logs/ad.replog nsslapd-pluginarg3:pae-ADUnicodeBase64Password nsslapd-pluginType: postoperationnsslapd-plugin-depends-on-type: database nsslapd-pluginInitfunc:paerep_postoperation_init nsslapd-pluginPath:/opt/Propero/properDirectory/lib/libpaerep-plugin.sonsslapd-pluginVendor: Propero Ltd. nsslapd-pluginDescription: ProperoExtensible Replication Plugin nsslapd-pluginVersion: 0.4nsslapd-pluginId: PAEREP Extensible Replication nsslapd-pluginEnabled:onLDAP Add

After an LDAP entry is added, each added LDAP attribute type is comparedwith the parameter list specified in the XSL stylesheet. If there's amatch, the XSLT Processor is run passing all available parameter valuesfrom the new LDAP entry.

In addition to LDAP attribute types, the built in parameters changetype,dn, modifiersname and time are also passed if they are defined in theXSL. See below for a description of these built in parameters.

LDAP Modify

The XSLT processing for an LDAP Modify is similar to LDAP Add. Thedifference is that only the attribute types that have actually changedare passed as parameters. This is done for efficiency. If an attributetype value changes that is not defined as a parameter in the XSLstylesheet, XSLT processing will not be performed.

XSLT processing is performed once for each attribute type modified.

In addition to LDAP attribute types, the built in parameters changetype,dn, modifiersname and time are also passed if they are defined in theXSL. See below for a description of these built in parameters.

Additional attribute types can be passed after an LDAP Modify even ifthose attribute types have not changed. This is sometimes required forLDAP Modify XSLT processing. These additional parameters are specifiedas plugin startup parameters 4 and beyond. See above.

LDAP Delete

The XSLT processing for LDAP Delete is very simple as no LDAP attributetype values are available after the entry has been deleted. The onlyparameters available are the built in parameters changetype, dn,modifiersname and time. These are passed if they are defined in the XSL.See below for a description of these built in parameters.

LDAP MODRDN

This plugin doesn't support the MODRDN LDAP operation. It may besupported in a future release.

XSL Parameters

Any LDAP attribute type such as uid, cn, mail etc. can be used as aparameter in the XSL stylesheet.

This plugin also allows some built in parameters to be used. These areas follows:

-   -   changetype—one of add, modify or delete    -   dn—the distinguished name of the LDAP entry added, modified or        deleted    -   modifiersname—the distinguished name of the LDAP user who made        the change.    -   time—the time the change took place given, as the number of        seconds since 00:00:00 GMT, Jan. 1, 1970. This value is used in        a slurpd changelog. See the man pages for slapd.replog.

Any parameters passed to the XSLT processing are automatically decryptedif they have been encrypted using the encryption routines as suppliedwith the Propero workspace software. See the XSL stylesheet examplebelow for details of how these parameters are used.

XSLT Processing

The plugin uses the C API to the Sablotron library as the XSLTprocessor. This is maintained by the Ginger Alliance Open ResourceCentre. See http://www.gingerall.org/charlie/ga/xml/p_sab.xml Sablotronprovides access to a set of standard Document Object Model (DOM)functions which are used to parse the XSLT stylesheets.

It is linked with the static Sablotron libraries to avoid a libraryfunction clash with an LDAP Function. This means that the plugin is notdependent on the Sablotron shared object libraries.

Message Based Load Balancing

One of the techniques provided by the Application Workspace System is amessage bus, which it uses for operations such as load balancing amongterminal servers and for security related resources. A message bus is acommunications abstraction (provided by code) which allows a requester(or any type of querying agent) to send a broadcast message asking forcertain information or requesting a particular response, Servers thatcan potentially provide the information or the requested service,subscribe to the messaging service and the particular messages that arerelevant to the information or services provided by the servers. Whenthe requester broadcasts a request, only those servers that can/desireto provide the information or service respond. In that way, therequestor knows what servers are available and/or appropriate to thedesired information or service.

Message based load balancing keeps the application logic of resourceselection simple, and also inherently provides up-to-date informationthat does not include information about resources that are not presentor not responding, and thus provides a basis upon which to constructhighly-available systems.

For example, the AWS uses message-bus based load balancing to determinewhich servers to use to launch remote application access requests. Thisallows the AWS to avoid use of central component to respond to loadbalancing queries, to ensure the receipt of updated informationregarding available servers, and to avoid the complexities of detectingserver unavailability, timeouts, etc. For example, the AWS sessionmanagement server components (such as Session & Connection Control 312in FIG. 3) can use the message bus to find out what terminal servers(e.g., remote applications terminal services 340 in FIG. 3) areavailable, and then in the surrounding code determine which one to usebased upon any AWS specified load balancing algorithm.

FIG. 39 is an example block diagram of a general message bus as used byan Application Workspace System. As described, message bus 3901 can beused for load balancing as well as for general service or resourcediscovery, and for high-availability work. When a load balancing queryor resource discovery query requires resolving, a querying agent (somecomponent of the AWS or other system) such as requestor process 3902broadcasts a message to message bus 3901 to which all possiblerespondents are listening/subscribed to. The message may includeelements of data that will be relevant to resolving the request, such asdata that indicates which of the possible respondents should respond.

Thereafter, servers, such as servers 3903, 3904, and 3905, respond tothe particular request. The querying agent 3902 then receives all thepossible responses to the original message within a defined timeoutperiod (controlled, for example, by the code invoked by the queryingagent to broadcast the message). This timeout period is relativelyshort, for example 10 seconds, and as such serves to filter out possiblerespondents that are not in a position to respond—either due to afailure, or due to overloading. In one embodiment, this timeout periodis defined as the time period for all responses to be received, and notas a timeout per possible respondent.

The querying agent 3902 then applies an algorithm to the elements ofdata returned from all the respondents to decide which is the mostappropriate respondent. In the case of a query to figure out where torun or access an application or data, the algorithm may be a loadbalancing algorithm.

Note that the message bus mechanism provided by the AWS also can be usedfor other purposes, such as voting and consistency checking.

Example pseudo-code of how the message bus is used to perform a loadbalancing algorithm across Terminal Servers for session management isincluded as Table 2, below. Note that the parameter “serversToQuery” isa list of possible servers that has been retrieved from LDAP. The loadbalancing algorithm employed in this code sorts the responding serversbased upon statistical information and then chooses which one to usebased upon the sort. For example, in the code shown below, thestatistics include the number of current sessions being serviced, thepercentage of memory being used, and the average processor time beingutilized. Other load balancing algorithms can be similarly incorporated.

TABLE 2  1 SDMessageManager statisticsRequest = new SDMessageManager(serversToQuery,  2 serverTimeout);  3 log.debug(“allocateNewSession -sending GetStatistics message”);  4 HashMap statisticsResponse =  5statisticsRequest.sendMessage(SDMessageManager.GET_STATISTICS);  6TreeMap sortedResponse = new TreeMap( );  7 // We produce a “score”based on the statistics, and then put the server  8 // name as a valueinto the TreeMap keyed by the score. The TreeMap is sorted, so the first 9 // item in the Map will be the one to use. If that can't be used,then the second is used  10 // and so forth. Note, however, thatresponding to a statistics query is taken to mean that the  11 // serveris alive and can accept connections.  12  13 // The statistics are:  14// Number of sessions  15 // Percentage of Committed Bytes Used  16 //Averaged processor utilization  17  18 // This results in an easypercentage scoring - for number of sessions for example 50 users  19 //can be selected as the maximum load  20  21 Iterator statisticsIterator= statisticsResponse.entrySet( ).iterator( );  22  23 while(statisticsIterator.hasNext( ))  24 {  25 try  26 {  27 Map.EntrystatisticsEntry = (Map.Entry)statisticsIterator.next( );  28 HashMapstatisticsMap = (HashMap)statisticsEntry.getValue( );  29  30 StringisAccepting = (String)statisticsMap.get(“ACCEPTINGCONNECTIONS”);  31  32if (isAccepting == null) // Downlevel systemmanager.  33 isAccepting =“TRUE”;  34  35 // Is this server accepting connections?  36  37 if (isAccepting.length( ) == 0 ∥ isAccepting.equalsIgnoreCase(“TRUE”) )  38{  39 // Compute our value...  40  41 float sessionLoadPercentage =Float.parseFloat ( (String)statisticsMap.get  42 (“TOTALSESSIONCOUNT”)); 43 sessionLoadPercentage = (sessionLoadPercentage * 100) /(float)MAX_SESSIONS;  44  45 float committedBytesPercentage =Float.parseFloat ( (String)statisticsMap.get  46(“COMMITTEDBYTESUSED”));  47 float processorPercentage =Float.parseFloat ( (String)statisticsMap.get  48 (“PROCESSORLOAD”));  49 50 float totalLoadPercentage = (sessionLoadPercentage +committedBytesPercentage +  51 processorPercentage) / 3;  52  53 //check the processorPercentage and committedBytesPercentage - if they'remore  54  55 // than e.g. 75% and 65% ignore this server  56  57 if(processorPercentage < maxProcessorPercentage &&committedBytesPercentage  58 < maxCommittedBytesPercentage) {  59  60 if(log.isDebugEnabled( )) {  61  62 log.debug (“allocateNewSession -Server ” + statisticsEntry.getKey( ).toString( ) +  63 “ has currentload (%) of ” + Float.toString (totalLoadPercentage));  64  65 }  66  67sortedResponse.put (new Float (totalLoadPercentage),statisticsEntry.getKey( ));  68  69 } else {  70 log.warn(“allocateNewSession - Server ” + statisticsEntry.getKey( ).toString() +  71  “ is overloaded, sessionLoadPercentage=” +sessionLoadPercentage +  72  “, committedBytesPercentage=” +committedBytesPercentage +  73  “, processorPercentage=” +processorPercentage);  74 }  75  76 }  77  78 }  79 catch(Exception E){log.error (E);}  80 }  81  82 //OK... first entry is...  83PAESessionImp chosenSession;  84  85 String chosenServerDn;  86  87 try 88 {  89 chosenServerDn = (String)sortedResponse.get(sortedResponse.firstKey( ));  90  91 // We won't know much of thedetails at this point (as there's no session there yet)  92  93log.debug(“allocateNewSession - identified server for application”+applicationDn);  94  95 chosenSession =(PAESessionImp)(PAESessionImp.newInstance(getLdapConnection( ),  96this));  97  98 }  99 catch (Exception E) 100 { 101 // Didn't work -perhaps no responses 102 103 log.error(“No servers responded - unable toallocate new session.”); 104 105 throw new NoServersAvailableException(); 106 }

The above code shows that this is a Session Manager implementation inthat it is implementing the interfaces of the session controller forTerminal Servers (e.g., PAESessionImp class is an implementation of thePAESession interface). Other algorithms for load balancing can besimilarly defined and integrated in an example AWS.

The underlying support for a message bus can be provided by anycompliant message bus provider. In the example embodiment used tosupport the AWS, which is JAVA based, the message bus is a JMS messagebus, for example, provided by MQSeries. Additional information on JMSmessage buses can be found in http://java.sun.com/products/jms/, whichis incorporated herein by reference.

In addition to using a message bus for session management, the messagebased load balancing techniques can be used to determine which server touse for implementing secure VPN services (such as the tunnel servicesoffered by the Security, Authentication and Other Support Services 314in FIG. 3) when a user logs onto a managed workstation running the AWSManager client code. Session management and the selection of securityservice resources share some common requirements which can be suitablyaddressed by the use of the AWS message bus load balancing techniques.For example, both scenarios share the following characteristics:

-   -   The information must be up-to-date—as a result, lookups in        central repositories are not appropriate as the central        repository information is typically only be updated        periodically.    -   The selected resource must be present—message based load        balancing has the advantage that if a resource doesn't respond,        then it will not be selected. Central repositories may contain        stale information—in such instances, a resource may be selected        that is unavailable.    -   If a central repository is not used, then attempting to query        many individual resources using traditional connection based        approaches is inappropriate mainly due to handling situations        when resources are not present—the timeout behaviors when        dealing with multiple connections require careful attention and        can be difficult to implement.

Using message bus load balancing, the AWS web services can select anappropriate tunnel server at the moment it is needed to provide theconduit for secure communications between an AWS client and the AWS Webservices.

Grid Location Services

Grid Location Services (“GLS”) represent an integration of the multicastDNS (mDNS) technologies with DNS technology to achieve transparentconfigurability of servers.

The AWS needs to support the ability to services to be added, removedand to fail over without reconfiguring all the entities that use thoseservices. The AWS implements a mechanism referred to as Grid LocationServices to provide this capability. In older systems, mDNS or otherbroadcast/multicast directory name service systems were used through anetwork to achieve transparent reconfigurability, but theimplementations of firewalls in modern networks prevent such servicesystems from being effective. There are only a few services that allfirewalls allow through, and DNS (Domain Name Service) is one of them.

In a DNS system, names such the server names contained in urls (alsoknown as fully qualified domain names) are mapped to network addressesanalogous to how a phone book resolves names to phone numbers but with(typically) multiple steps of translation for all portions of a networkaddress. The directory, or portions of it, are typically replicatedthroughout a networked environment, but when a change to a mapping ofdomain name to network address occurs, this change needs to bepropagated to the DNS servers that implement the directory. Thus, when aserver address fails, or when the network is configured there is a delayto await the change taking effect. In addition, many small localnetworks do not support a DNS server, and so use other ways to map theaddress to a final destination—a node on the local network. In addition,as DNS does not check the state of any addresses that it provides (asdownstream or caching servers may be providing the address), there isalso the possibility that the final hop to a physical machine on a localnetwork will not properly result in a working destination.

mDNS protocols offer a way to provide such mappings without the use of aDNS. Thus, smaller or localized networks may implement mDNS to figureout which computing resource is response to a service request. In mDNS,a request for a service is reconciled with the provider of a serviceusing an IP multicast protocol without a DNS server being implemented.When devices fail, or are reconfigured, they simply don't respond, orrespond as appropriate to the service request.

As mentioned, many of today's firewall systems do not allow mDNSmessages to pass through the firewall. The AWS Grid Location Servicesaddress these problems by allowing remote computers and LANs to use aDNS name and the DNS protocol to resolve a name to an IP address, eventhough the “last hop” of the DNS resolution process is actually achievedusing mDNS. Thus, the devices can be reconfigured at will locally (oreven fail) transparent to requesting systems that access them remotely.

Technically, Grid Location Services is a combination of DNS and mDNS.mDNS is used to locate services on the same LAN, and a DNS to mDNSbridge allows entities not resident on the same LAN to take advantage ofthe capabilities of mDNS to locate services on that LAN.

FIG. 40 is an example block diagram that illustrates how AWS GridLocation Services work within a LAN and across LANs. Within LAN A 4010,workstations, such as computing systems 4012-4014, locate mDNS serviceswithin their LAN by using mDNS directly through mDNS server 4011. Remoteservices are located across a network, such as via wide area network4001, using the DNS, for example via the DNS/mDNS bridge server 4021,which communicates using mDNS on LAN B 4020 through mDNS connection4022. For example, the DNS/mDNS bridge server 4021 within LAN B isconfigured so that the subdomain “grid” of “lanb.foo.com” is handled byacross the mDNS connection 4022. As a result, a query from any DNSclient (for example, computing system 4013 on LAN A 4010) for the name“collectionserver.grid.lanb.foo.com” would result in the name“collectionserver” being resolved ultimately using mDNS services4023-4025 on LAN B 4020.

Note that this is not an implementation of what is sometimes termed“Dynamic DNS” in that the DNS servers in this invention are not updated.Rather, they always return a 0 “time to live” for all responses so theyare always re-queried, and each time they will use the state of the MDNSsystem to resolve the DNS query.

In an example embodiment of the AWS Grid Location Services, the GLSsubsystem (the DNS to mDNS bridge), for example, bridge server 4021 inFIG. 40, comprises two server components:

-   -   A server process (GLSDNS) that responds to DNS requests based on        the contents of a file (the “registration” file);    -   A server process (GLSMDNS) that is a registered mDNS node that        alters the contents of the above registration file based on mDNS        registrations.        The GLSDNS process is not the same as a standard DNS        server—standard DNS servers load information from a file, but        then view that information as static and tend to respond to        queries without re-querying the file. GLSDNS uses the contents        of the file for *each and every request it receives* and        responds to those requests setting the TTL (time to live) to 0        to ensure that the response is not cached by any downstream        components. This ensures that if a name needs to be resolved        again, it will result in another query being sent to GLSDNS.

The GLSMDNS process registers as an MDNS node with a configurable domainand for a number of different service types (see below for exampleusage), and listens for other registrations in that domain. When otherregistrations are received, it updates the registration file—this inessence ensures that the registration file contains all of the names andassociated IP addresses of nodes registered in a particular domainproviding a particular service. In addition, when nodes are no longerpresent, their information will be removed from the registrations fileby the GLSMDNS process.

GLSMDNS can also be extended with particular plug-ins that can checkwhether a server that is providing a service type is actually providingthat service. For example, if the GLSMDNS process is monitoring serversthat register LDAP directory services, then GLSMDNS will have a plug-inthat will periodically perform LDAP queries against all the servers inthe registration file, and for those that do not respond correctly, notinclude that node in the list of addresses that correspond to thatservice type in the registration file. mDNS uses a convention ofunderscores in service names—GLSMDNS strips these off when creating DNSnames that map to service names.

As an example of the use of AWS Grid Location Services, suppose 4 mDNSnodes exist in the .local. domain as follows:

Name Service(s) IP Address Notes PC01 _ldap._tcp 192.168.100.41 Has anLDAP server PC02 _ldap._tcp 192.168.100.42 Has an LDAP _jms._tcp serverand a JMS server PC03 _http._tcp 192.168.100.43 Has a web server PC04_rdp._tcp 192.168.100.44 Terminal ServerIn this example, there are a number of different service types,including LDAP services, JMS services, terminal services, and httpservices. GLSMDNS may have a plug-in to monitor each service type, butLDAP is the one that is commonly used in an example AWS. GLSMDNSmonitors mDNS messages for the .local. domain and having receivedregistrations for the above 4 nodes will write out a registration filethat includes the following contents:

# Hosts

PC01=192.168.100.41

PC02=192.168.100.42

PC03=192.168.100.43

PC04=192.168.100.44

# Services

LDAP=192.168.100.41, 192.168.100.42

JMS=192.168.100.42

HTTP=192.168.100.43

RDP=192.168.100.44

In this example, GLSDNS is configured to be the authoritative DNS serverfor the domain WORKSPACE.INT. GLSDNS responds to queries for names inthe WORKSPACE.INT domain by using the registration file created from themDNS information.

As a result, a DNS query for pc01.workspace.int would get the response192.168.100.41, and a DNS query for http.workspace.int would get192.168.100.43. GLSDNS uses each service address it finds in turn, sothat a DNS query for ldap.workspace.int may return 192.168.100.41 or192.168.100.42.

This last example demonstrates how the monitoring plug-ins operate—ifthe GLSMDNS monitoring plug-in for LDAP failed to retrieve a correctLDAP response to the test query, it would remove that node from the LDAPlist thus ensuring that clients who are requesting the service LDAP willonly receive the IP address of a working LDAP service.

By combining mDNS and DNS, a number of features of both are no longeravailable—e.g., mDNS has a facility for providing the port number of aservice as well as the address, and DNS has a strong focus on cachingresults to lower network traffic. Neither of which are available usingGLS.

However, the advantages of using the GLS approach are several. Serversand services can be added to an embodiment of the AWS without the needfor the configuration that DNS systems require and the AWS candynamically address whether those servers and services are present ornot. Also, service queries can take into account whether the service isactually functioning—this is an important part of high availability.Moreover, the GLS functionality is available to any client systems thatuse DNS without the requirement for additional client side software.

Additional information on DNS is provided in the DNS Specification RFC1035: http://www.ietf.org/rfc/rfc1035.txt. Details on using DNS tolocate services is provided in RFC 2782: http://rfc.net/rfc2782.html.Details on using mDNS are available in the mDNS Specification:http://files.multicastdns.org/draft-cheshire-dnsext-multicastdns.txt.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in the Application Data Sheet, including but not limited to U.S.Provisional Patent Application No. 60/752,208 entitled “VIRTUALIZEDAPPLICATION WORKSPACES,” filed on Dec. 19, 2005, is incorporated hereinby reference, in its entirety.

From the foregoing it will be appreciated that, although specificembodiments of the description have been described herein for purposesof illustration, various modifications may be made without deviatingfrom the spirit and scope of the invention. For example, the methods andsystems for performing entitlement resolution and packaging discussedherein are applicable to other architectures other than a Windows-basedarchitecture and in non “online” environment. For example, theseparation of user administration and application administration can beintegrated into a group of peer computer systems connected together. Themethods and systems discussed herein are applicable to differingprotocols, communication media (optical, wireless, cable, etc.) anddevices (such as wireless handsets, electronic organizers, personaldigital assistants, portable email machines, game machines, pagers,navigation devices such as GPS receivers, etc.).

1. A method in a computing system for performing automated electronicreplication of a first directory data repository in a first data formatto a second directory data repository in a second data format, whereinthe first data format is different from the second data format,comprising: providing and storing in a memory of a computing system anXSLT definition, the XSLT definition comprising a plurality of rules fortransforming directory data in the first data format to a representationin the second data format; upon detecting a change to at least one entryin the first directory data repository, automatically invoking an XSLTprocessor to retrieve the stored XSLT definition and process the XSLTdefinition to automatically generate, in the second data format, a logof the change to the at least one entry; on a periodic basis, providingthe log of the change to the at least one entry to an applicationservice associated with the second directory data repository such thatthe change to the at least one entry in the first directory datarepository can be automatically replicated in the second directory datarepository in the second format; and wherein the first directory datarepository uses an LDAP protocol and the second directory datarepository uses an Active Directory protocol and the method performsautomatic replication of an LDAP directory to an Active Directorydirectory.
 2. The method of claim 1 wherein the first and seconddirectory data repositories are used to provide authentication services.3. The method of claim 1 used to provide an audit log in a data formatthat is distinct from the first data format.
 4. The method of claim 1provided by a plug-in code module.
 5. The method of claim 1 wherein thechange to the at least one entry in the first directory data repositoryis at least one of an operation to add an entry, an operation to modifyan entry, or an operation to delete an entry.
 6. The method of claim 1wherein attribute mappings are specified by the stored XSLT definition.7. The method of claim 1 wherein the first directory data repository isstored in a first directory server and wherein the second directory datarepository is stored in a second directory server.
 8. The method ofclaim 1 wherein the change to the at least one entry in the firstdirectory data repository is an LDAP Modify, and further comprising:processing the LDAP Modify by performing XSLT processing only for LDAPattribute values that have been changed, and by not performing XSLTprocessing for LDAP attribute values that have not been changed.
 9. Themethod of claim 1, further comprising: parsing the XSLT definition,wherein the parsing of the XSLT definition is performed only atinitialization time of a plug-in that performs the method.
 10. Themethod of claim 1, further comprising: decrypting encrypted parameterspassed to the XSLT processor.
 11. A computer-readable medium containingcontents that, when executed, causes a computing system to perform amethod comprising: in response to detecting an operation performed on atleast one entry of a first directory data repository, the operationspecified in accordance with an input data format, automaticallyexecuting a processor, configured, when executed, to: determine one ormore stored XSLT stylesheet definitions for transforming directory datain the input data format to directory data in an output data format, theoutput data format being different from the input data format;automatically generate a representation in the output data format of theoperation performed on the at least one entry of the first directorydata repository such that the operation can be automatically replicatedusing the output data format; and wherein the input data format isspecified in accordance with an LDAP directory protocol and the outputdata format is specified in accordance with an Active Directory protocoland the method performs automatic replication of an LDAP directory to anActive Directory directory.
 12. The computer-readable medium of claim 11wherein the computer-readable medium is a memory in a computing device.13. The computer-readable medium of claim 11, the method performed by afirst directory server, and wherein the method is used to replicate anLDAP directory in one or more other directory servers.
 14. Thecomputer-readable medium of claim 11, the method further comprising: ona periodic basis, providing the generated representation in the outputdata format to an application service associated with a second directorydata repository such that the at least one entry in the first directorydata repository can be automatically replicated in the second directorydata repository.
 15. The computer-readable medium of claim 11 whereinthe generated representation in the output data format is at least oneof a change log, an audit log, a representation used to authenticatedata, or a representation used to synchronize data.
 16. Thecomputer-readable medium of claim 11 wherein the operation performed onthe at least one entry of the first directory data repository is atleast one of a modify operation, an add operation, or a deleteoperation.
 17. The computer-readable medium of claim 11 wherein thecontents are configured to be executed by a software plug-in module, andthe one or more stylesheet definitions can be modified to generate a newtransformation transparent to the plug-in module.
 18. Thecomputer-readable medium of claim 11, wherein the method furthercomprises: parsing the one or more XSLT stylesheet definitions, whereinthe parsing of the one or more XSLT stylesheet definitions is performedonly at initialization time of a plug-in that performs the method. 19.The computer-readable medium of claim 11, wherein the method furthercomprises: decrypting encrypted parameters passed to an XSLT processor.20. A computing system for providing automated replication of directorydata in data repositories stored according to distinct data formats,comprising: a first data repository configured to store thereindirectory data in a first data format; and a memory having a directoryservices plug-in module stored thereon, configured, when executed, to:retrieve an XSLT stylesheet that provides one or more definitions fortransforming directory data in the first data format to a second dataformat; upon detecting a change to directory data stored in the firstdata repository, invoke an XSLT processor with the retrieved stylesheetto provide in a second data format a record of the change in thedirectory data, the record configured to be automatically consumable bya software service connected with a second data repository; and whereinthe first directory data repository uses an LDAP protocol and the seconddirectory data repository uses an Active Directory protocol and thedirectory services plug-in module performs automatic replication of anLDAP directory to an Active Directory directory.
 21. The computingsystem of claim 20 wherein the stylesheet is modified to accommodate newconfiguration parameters in a manner that is transparent to the plug-inmodule.
 22. The computing system of claim 20 wherein the first andsecond data repositories are used to provide authentication services.23. The computing system of claim 20 wherein the record is used toprovide an audit log.